Printable View
Hi,
I have to write a SQL to insert records into my table(The table has
a large amounts of fields,more than 100).
The SQL is a CString, but it is too big and exceeds the
maxium length of a CString. Please help me how can I
create a string with any huge length? Code examples would
be more appreciated.Or any method I can use to solve this problem?
Thanks a lot.
wang
"exceeds the maxium length of a CString"
really?
CString hasn't maxium length.it use "new" internal
Well...sorry but this is not true...to keep track of the length 'CString' uses an integer...thus it can only hold up to INT_MAX - 1 (2,147,483,646) characters... :cool:Quote:
Originally posted by FINIX
"exceeds the maxium length of a CString"
really?
CString hasn't maxium length.it use "new" internal
wangnanjing, please do not cross-post your questions to several forums. Thank you very much...
Quite true, this is a limit imposed in CString::AllocBuffer by an ASSERT.Quote:
Well...sorry but this is not true...to keep track of the length 'CString' uses an integer...thus it can only hold up to INT_MAX - 1 (2,147,483,646) characters...
But FINIX is right. An "Out of memory" exception may be thrown when try to allocate memory for INT_MAX-1 characters.
I think the point is being missed. I really doubt the CString is 2.1 gigs of data....can we get to the real issue please?
Who did that huge SQL statement?
Somehow it was made by some erudite designer(s), dragging/dropping
some squares and arrows, then automatically generated the SQL statement? :D
Anyhow, that statement must be reviewed to be optimized, parsed in few smaller, and so on.
You can see from my previous post, that if somebody can solve the problem as you wish,Quote:
The SQL is a CString, but it is too big and exceeds the
maxium length of a CString. Please help me how can I
create a string with any huge length?
for sure you'll have got problem with the memory.
That's it!
Umm yea....what I said...Quote:
Originally posted by ovidiucucu
Who did that huge SQL statement?
Somehow it was made by some erudite designer(s), dragging/dropping
some squares and arrows, then automatically generated the SQL statement? :D
Anyhow, that statement must be reviewed to be optimized, parsed in few smaller, and so on.
You can see from my previous post, that if somebody can solve the problem as you wish,
for sure you'll have got problem with the memory.
That's it!
Go ahead...or what was the reason of the post?Quote:
Originally posted by Mick_2002
...can we get to the real issue please?
I do not see that....'CString' has a limit...disregarding whether 'new' is used or not...Quote:
Originally posted by ovidiucucu
But FINIX is right.
I don't know, what was the reason for the post?Quote:
Originally posted by Andreas Masur
Go ahead...or what was the reason of the post?
Well...joking is okay sometimes...but there is a fine line between sometimes and too many times... ;)Quote:
Originally posted by Mick_2002
I don't know, what was the reason for the post?
Who was joking?Quote:
Originally posted by Andreas Masur
Well...joking is okay sometimes...but there is a fine line between sometimes and too many times... ;)
How do you create your string??
If it is something like this:
CString str = "very huge string";
you can do the following:
CString str = "string shorter";
str += "the rest of the string";
I think the point of Mick's post is it is very unlikely that the CString
is really 2.1G so something else must be going on.