Received: from squire.barchord.com (squire.barchord.com [216.194.67.18]) by postgresql.org (Postfix) with ESMTP id 456B8474E42 for ; Mon, 15 Apr 2002 23:19:55 -0400 (EDT) Received: from jester (CPE00045a0f27e3-CM00803785c5e0.cpe.net.cable.rogers.com [24.103.22.88]) by squire.barchord.com (Postfix) with SMTP id 84AAB100 for ; Mon, 15 Apr 2002 23:19:56 -0400 (EDT) Message-ID: <0a9401c1e4f5$8f2ac5b0$8001a8c0@jester> From: "Rod Taylor" To: "Hackers List" References: <200204160258.g3G2wpG01075@candle.pha.pa.us> Subject: Re: [PATCHES] [SQL] 16 parameter limit Date: Mon, 15 Apr 2002 23:19:45 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Archive-Number: 200204/765 X-Sequence-Number: 21429 On the note of NAMEDATALEN, a view in the INFORMATION_SCHEMA definition is exactly 2 characters over the current limit. ADMINISTRABLE_ROLE_AUTHORIZATIONS Not that it's a great reason, but it isn't a bad one for increasing the limit ;) -- Rod Taylor > Are we staying at 16 as the default? I personally think we can > increase it to 32 with little penalty, and that we should increase > NAMEDATALEN to 64.