Tomasz Sokólski wrote:
> Axel Schwenke napisa?(a):
>
>> Wait! You have a table with 1000 columns?
>> Now that's a weird design.
>
>
> That's not my design - I just work with problems with such designs
> BTW - how to store data from forms - where each form has 1000 questions.
> Each record is one filled form which contains 1000 answers.
>

Read up on database normalization. A much better way would be to have a
second table with three columns - userid, questionid and answer.

>>> DBD::mysql::st execute failed: Thread stack overrun:
>>> 186116 bytes used of a 196608 byte stack, and 10788 bytes needed.
>>> Use 'mysqld -O thread_stack=#' to specify a bigger stack.
>
>
> Thank you very much - it helped.
>
>> Please note: this is a normal SQL error, reported from mysqld to the
>> client. Mysqld did not crash. I restarted mysqld with thread_stack=512K
>> in my.cnf and this time my test program finished without a problem.
>
> > Conclusion: the SQL parser eats memory if it has to parse long
> > expressions. You can compensate by configuring a bigger stack.
> > I cannot explain why your mysqld crashed. Maybe the stack isn't
> > checked in 5.0.22 or your specific build of it.
>
> Very weird - this is standard version from www.mysql.org running on
> Slackware 10.2 with 2.6.17.7 kernel.
>
>> PS: I could not create a 1000 x FLOAT table in InnoDB because that
>> would have exceeded the maximum row length. So I used 999.
>
>
> We use MyIsam engine.
>
>> PPS: find my test program attached
>
>
> Thank's a lot!


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================