Re: Design strategy for table with many attributes

On 7/4/24 15:37, Lok P wrote:
> Or say, what is the maximum number of columns per table we should
> restrict? Should we break the single transaction into multiple tables
> like one main table and other addenda tables with the same primary key
> to join and fetch the results wherever necessary?

900 columns makes my head hurt badly...

The neophyte will design a table with a separate field for each type of
phone number that may be encountered.  The experienced designer will
move all phone numbers to its own table, where each entry/row contains a
reference link, a "number_type" field, and a field with the actual
number in it...Three fields in a table that is manageable and can be
queried/modified without stressing the database server.