Re: 1600 Column limit..
От | Williams, Travis L, NPONS |
---|---|
Тема | Re: 1600 Column limit.. |
Дата | |
Msg-id | AB815D267EC31A4693CC24D234F8291602E59CD7@ACCLUST02EVS1.ugd.att.com обсуждение исходный текст |
Ответ на | 1600 Column limit.. ("Williams, Travis L, NPONS" <tlw@att.com>) |
Ответы |
Re: 1600 Column limit..
Re: 1600 Column limit.. |
Список | 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@mobile.mp] Sent: Thursday, November 14, 2002 1:35 PM To: Williams, Travis L, NPONS Cc: pgsql-general@postgresql.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.
В списке pgsql-general по дате отправления: