limitation on the number of fields in a query?

cpeppler

I've been pulling my hair out with a simple query, that happens to have a lot of fields (21).

When I query using "select * from Event...", the query works fine.

I needed to do some date formatting on one of the fields, so I broke the fields out individuallly, and I got an "Invalid resource" when I went to do mysql_fetch_array after the query.

I started cutting back on the number of individually selected fields, and the query started working again.

I am using PHP v4.1.2, Apache/1.3.23, and MySQL 3.23.45.

Are there limits to the number of fields that I don't know about? Are there any special things I should be doing?

Thanks in Advance for any help.

Charlie Peppler

cpeppler

I have continued troubleshooting the problem, and have found that the issue is NOT related to the number of fields, but instead, having to with fetching a field of type TEXT.

All the VARCHARS work great, but for some reason, it's crapping out on fetching a field of type TEXT.

Any ideas why the TEXT field works differently from the VARCHARs?

Charlie

mykg4orce

VARCHAR is usually used for variables, length is 1 to 255 and trailing spaces are removed.

TEXT is obviously for storing anytype of characters...and also has a specifed but very large length...

TodManPlaa

Hi,

Select the TEXT type fields last in your SELECT statement and the problem should go away.

If that doesn't help, lemme know.

Hope this helps

cpeppler

After doing some continued troubleshooting, I finally found out the source of the problem.

I had named a text field desc. When I included it in the list of field names, I think the parser picked it up as a keyword (as in DESCending, sort). When I put backquotes around it, Viola! It worked!

I have since renamed the field (bad idea to name fields that match parser keywords).

Thanks goes to phpMyAdmin, where studied the queries it creates, and got the idea for surrounding the field with backquotes. All running now.

Charlie Peppler