Received: from netcom12.netcom.com (zalman@netcom12.netcom.com [192.100.81.124]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA14535 for ; Tue, 1 Jun 1999 02:30:19 -0400 (EDT) (envelope-from zalman@netcom.com) Received: (from zalman@localhost) by netcom12.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) id XAA23711; Mon, 31 May 1999 23:30:10 -0700 (PDT) From: Zalman Stern Message-Id: <199906010630.XAA23711@netcom12.netcom.com> Subject: Re: [SQL] Column name's length To: maillist@candle.pha.pa.us (Bruce Momjian) Date: Mon, 31 May 1999 23:30:09 +1700 (PDT) Cc: tpham@mail.priority.net, pgsql-sql@postgreSQL.org In-Reply-To: <199906010241.WAA06667@candle.pha.pa.us> from "Bruce Momjian" at May 31, 99 10:41:14 pm X-Mailer: ELM [version 2.4 PL25] 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.) -Z-