MySQL save problem (BIG string)
#4

You have two options that i can think of.

1): See if you can increase the array size to fit the query (without the stack/heap collision warning)
2): Do several queries.

I'd favor increasing the array size. It wont be too bad on memory because it's a local variable and will be destroyed when it goes out of scope, and it will be faster than several queries.

If you get the stack/heap warning you should do several queries.

EDIT: Also might be better if you sort all that data into separate tables.
Reply


Messages In This Thread
MySQL save problem (BIG string) - by ryansheilds - 24.06.2012, 11:43
Re: MySQL save problem (BIG string) - by Grand_Micha - 24.06.2012, 11:54
Re: MySQL save problem (BIG string) - by ryansheilds - 24.06.2012, 12:09
Re: MySQL save problem (BIG string) - by iggy1 - 24.06.2012, 12:30
Re: MySQL save problem (BIG string) - by ryansheilds - 24.06.2012, 12:40
Re: MySQL save problem (BIG string) - by iggy1 - 24.06.2012, 12:47
Re: MySQL save problem (BIG string) - by ryansheilds - 24.06.2012, 12:58
Re: MySQL save problem (BIG string) - by ryansheilds - 24.06.2012, 21:02
Re: MySQL save problem (BIG string) - by Badger(new) - 24.06.2012, 21:28
Re: MySQL save problem (BIG string) - by ryansheilds - 24.06.2012, 21:53

Forum Jump:


Users browsing this thread: 2 Guest(s)