Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA15326 for ; Tue, 1 Jun 1999 02:37:36 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id CAA17071; Tue, 1 Jun 1999 02:36:52 -0400 (EDT) From: Bruce Momjian Message-Id: <199906010636.CAA17071@candle.pha.pa.us> Subject: Re: [SQL] Column name's length In-Reply-To: <199906010630.XAA23711@netcom12.netcom.com> from Zalman Stern at "May 31, 1999 11:30:09 pm" To: Zalman Stern Date: Tue, 1 Jun 1999 02:36:52 -0400 (EDT) CC: tpham@mail.priority.net, pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > I recompiled my server with support for longer (128 character max) table > names. (This was a bit tricky because you have to change things in two > places.) 32 character limits are rather low. 64 or 128 are more reasonable. > (Yes, I know this is controversial. The problem I was having is analogous > to the SERIAL problem: table names are made by concatenating together a few > fields. Each of thee fields can reasonably be 15 or 20 characters. So while > 32 characters is fine for a single human generated identifier, it is not > long enough for other purposes.) And I assume it is working fine? -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026