On 6/15/2016 9:39 PM, Shaun Cutts wrote:
Is there a reason besides “its bad design” to disallow tables with many columns?
it would require significantly different internal architecture optimized
for said huge rows.
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-general
On 16/06/16 16:39, Shaun Cutts wrote:
The opinion of database developers is that using more than 1664 columns is bad
design, so that the current maximum number of columns is not onerous.
When I simply built applications on top of databases, I was of the same opinion.
However, now my job is to
Shaun Cutts writes:
> Is there a reason besides âits bad designâ to disallow tables with many
> columns?
There are numerous implementation problems you'd have to overcome.
There are illuminating comments in htup_details.h:
* MaxTupleAttributeNumber limits the number of (user) columns in a t
The opinion of database developers is that using more than 1664 columns is bad
design, so that the current maximum number of columns is not onerous.
When I simply built applications on top of databases, I was of the same opinion.
However, now my job is to perform some sort of analysis on data fr
