[SOLVED] Limit to ammount of fields in a table?

[jordanwb]

I'm making a website for a friend who is a mortgage broker. He wants me to make an online application page and he showed me a list of fields he wants. There are literally at least 100 fields - about 12 are required (thank god for me), so I was wondering: Would having 100+ fields in a table would lead to any problems?

[revraz]

Shouldn't, but you may be able to review the list and see if 100+ are really needed.

[jordanwb]

but you may be able to review the list and see if 100+ are really needed.

 

I'm not really in the position to do that. It would make for one really long SQL statement.

[shlumph]

You could probably normalize it, breaking it these 100 fields into many tables instead of just one huge dump.

 

Look for fields that can easily group together and put them in their own table. For more info: http://en.wikipedia.org/wiki/Database_normalization

 

[revraz]

Sure you are, you are the designer right?

 

but you may be able to review the list and see if 100+ are really needed.

 

I'm not really in the position to do that.

[jordanwb]

Sure you are, you are the designer right?

 

Yes but I'm designing it as to how he wants it, and he wants those fields.

[Mchl]

There's such thing as vertical partitioning. You can split columns into two or more tables with one-to-one relation.

 

Have frequently used columns and fields in one table, and rarely used columns in another. This will let you improve performance a little.