Search Postgresql Archives

Re: Beyond the 1600 columns limit on windows

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Evandro's mailing lists (Please, don't send personal messages to this address) wrote:
Sorry,
 It has nothing to do with normalisation. It is a program for scientific
applications.

It has everything to do with normalisation. You appear to be pushing application presentation issues into the structure of your database. If SQL allowed you, this would break 1NF.

Data values are broken into column to allow multiple linear regression and
multivariate regression trees computations.

Sounds like you want an array then (or perhaps several arrays).

 Even SPSS the most well-known statistic sw uses the same approach and data
structure that my software uses.

Ah - and they've made a good choice?

Probably I should use another data structure but would not be as eficient
and practical as the one I use now.

The structure you use inside your application and the data definition used by the database are two separate things. You presumably are doing some transformation of data on fetching it anyway - I'd switch rows-columns over then.

--
  Richard Huxton
  Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux