From: | "Williams, Travis L, NPONS" <tlw(at)att(dot)com> |
---|---|
To: | "Joe Tomcat" <tomcat(at)mobile(dot)mp> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 1600 Column limit.. |
Date: | 2002-11-14 01:40:31 |
Message-ID: | AB815D267EC31A4693CC24D234F8291602E59CD7@ACCLUST02EVS1.ugd.att.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The reason we have that is we have 23 slots in a shelf (of equipment)
and we have 23 ports in a slot. We are tracking 3 different items per
port.. so we have 23 x 23 which is 529 x 3 which is 1587 individual
items to track of which they are all a single digit. You add into that
some misc. stuff like shelf name and poll_time and it becomes a mess..
I just split them into 3 seperate tables.
Travis
-----Original Message-----
From: Joe Tomcat [mailto:tomcat(at)mobile(dot)mp]
Sent: Thursday, November 14, 2002 1:35 PM
To: Williams, Travis L, NPONS
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] 1600 Column limit..
On Wed, 2002-11-13 at 17:23, Williams, Travis L, NPONS wrote:
> Is this set in stone.. or is there somewhere you can change this.. and
will changing it cause upgrade problems in the future..
If you are trying to have 1600 columns in a table, you probably have
made a design mistake in your table design. You should take a look at
some database design books to see if you can change the structure.
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Hirt | 2002-11-14 01:52:51 | Re: 1600 Column limit.. |
Previous Message | Williams, Travis L, NPONS | 2002-11-14 01:23:07 | 1600 Column limit.. |