if there is some no-SQL database supporting ACID + generic queries like a SQL database, I would consider it.
However, the column limit is the problem, no the database. 1200 cols are reasonable for standard problems. Having a Postgresql supporting thousands of columns will be useful in Machine Learning and similar domains.
On 4/24/19 3:17 PM, pabloa98 wrote: > Hello > > Sadly today we hit the 1600 columns limit of Postgresql 11. > > How could we add more columns? > > Note: Tables are OK. We truly have 2400 columns now. Each column > represents a value in a matrix. > > We have millions of rows so I would prefer not to transpose each row to > (x, y, column_value) triplets because it will make all our code more > difficult of what it is. > > Any help, very appreciated.
Is a relational database the proper tool for the job?
