> On 09/06/2023 16:00 CEST Wim Bertels wrote:
>
> Joe Conway schreef op vr 09-06-2023 om 09:16 [-0400]:
> > On 6/8/23 22:17, Pat Trainor wrote:
> > > I need to have a very large matrix to maintain & query, and if not
> > > (1,600 column limit), then how could such data be broken down to
> > > work
Joe Conway schreef op vr 09-06-2023 om 09:16 [-0400]:
> On 6/8/23 22:17, Pat Trainor wrote:
> > I need to have a very large matrix to maintain & query, and if not
> > (1,600 column limit), then how could such data be broken down to
> > work?
>
> 100,000 rows *
> 100,000 columns *
> 8 bytes
On 6/8/23 22:17, Pat Trainor wrote:
Imagine something akin to stocks, where you have a row for every stock,
and a column for every stock. Except where the same stock is the row &
col, a number is at each X-Y (row/column), and that is the big picture.
I need to have a very large matrix to mainta
> On 9 Jun 2023, at 04:17, Pat Trainor wrote:
(…)
> Imagine something akin to stocks, where you have a row for every stock, and a
> column for every stock. Except where the same stock is the row & col, a
> number is at each X-Y (row/column), and that is the big picture. I need to
> have a v
Experts,
A very high level question... Subject sums it up.
I love PGSQL, but I don't know if it is a good fit for this back-end... I
hope it is.
Imagine something akin to stocks, where you have a row for every stock, and
a column for every stock. Except where the same stock is the row & col, a
