Posts: 424
Threads: 21
Joined: Jun 2008
Reputation:
0
query[60] needs to be bigger, try [100]
Posts: 995
Threads: 71
Joined: Jul 2008
Reputation:
0
I would get rid of all query strings and add a new query[1000]; to the top for all SQL queries big or small..
Posts: 424
Threads: 21
Joined: Jun 2008
Reputation:
0
64 would still be too small....
AND WHY THE HECK WOULD YOU MAKE A STRING 1000 BIG? EVER?
Posts: 2,938
Threads: 162
Joined: May 2010
09.08.2010, 16:45
(
Last edited by Kar; 01/08/2011 at 11:40 PM.
)
Quote:
Originally Posted by Daren_Jacobson
64 would still be too small....
AND WHY THE HECK WOULD YOU MAKE A STRING 1000 BIG? EVER?
|
Sorry for my post ):
Posts: 918
Threads: 7
Joined: Aug 2007
Quote:
Originally Posted by Kar
biggest idiot ever
|
Agreee...
Posts: 424
Threads: 21
Joined: Jun 2008
Reputation:
0
Talking about me or coole?
Posts: 2,938
Threads: 162
Joined: May 2010
09.08.2010, 16:56
(
Last edited by Kar; 20/05/2012 at 02:13 AM.
)
....
Posts: 424
Threads: 21
Joined: Jun 2008
Reputation:
0
okay then, explain yourself.
Posts: 2,938
Threads: 162
Joined: May 2010
[1000] will save u from doing new string [128] all the time>? and less usage of stack or byte thing w/e it is that makes the compiler show the coding header thing.
if you dont know what it is take one of your stocks and put it over ongamemodeinit and u'll see what i mean.
Posts: 424
Threads: 21
Joined: Jun 2008
Reputation:
0
okay first he said put 1000 over every query, so this is not a global, but still:
1000 exists for all runtime,
or
100 exists for a few milliseconds.
Posts: 2,938
Threads: 162
Joined: May 2010
well his query's are big.. it all depends on you tbh. put what you want. if it says size doesn't not match definition just try to put something higher. i can't really explain good enough you wont understand
Posts: 424
Threads: 21
Joined: Jun 2008
Reputation:
0
it wouldn't give that error but whatever.
@ScottCFR Did you ever fix it?