Received: from lerami.lerctr.org (lerami.lerctr.org [207.158.72.11]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAHH0as53175 for ; Fri, 17 Nov 2000 12:00:36 -0500 (EST) (envelope-from ler@lerctr.org) Received: (from ler@localhost) by lerami.lerctr.org (8.11.1/8.11.1/20001028) id eAHGx0309909 for pgsql-sql@postgresql.org; Fri, 17 Nov 2000 10:59:00 -0600 (CST) (envelope-from ler) Date: Fri, 17 Nov 2000 10:58:59 -0600 From: Larry Rosenman To: sqllist Subject: Re: Requests for Development Message-ID: <20001117105859.A9780@lerami.lerctr.org> References: <3A0AD389.647EE03A@agliodbs.com> <200011150953.EAA01528@jupiter.jw.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <200011150953.EAA01528@jupiter.jw.home>; from janwieck@Yahoo.com on Wed, Nov 15, 2000 at 04:53:02AM -0500 X-Mailer: Mutt http://www.mutt.org/ X-Archive-Number: 200011/137 X-Sequence-Number: 168 * Jan Wieck [001117 08:26]: > > triggered the error would be enormously helpful (I can't tell you the > > number of times I've gotten "Error at or near ')'" in a huge DDL > > statement. > > That's a general problem of a lex/yacc parser and I'm not > sure how to force it to be a little more explanative. Maybe > we have a chance to grab something from the lex input buffer, > but IIRC that's unsafe because nobody knows how much of that > is already eaten into yacc tokens. I was reading the O'Reilly Lex & YACC book over the weekend, and they have some tricks that should make this easier. If someone wants to look into it.... LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749