Received: from yara.imsd.uni-mainz.de (yara.IMSD.Uni-Mainz.DE [134.93.144.68]) by postgresql.org (Postfix) with ESMTP id 3010B4768ED; Fri, 12 Apr 2002 03:02:05 -0400 (EDT) Received: (from smap@localhost) by yara.imsd.uni-mainz.de (8.9.3/8.9.3/lxs_5.2) id JAA02111; Fri, 12 Apr 2002 09:02:32 +0200 Received: from hermes.imsd.uni-mainz.de(134.93.64.80) by yara.imsd.uni-mainz.de via smap (V2.1/2.1+anti-relay+anti-spam) id xma002103; Fri, 12 Apr 02 09:02:31 +0200 Received: from magnus (unverified [134.93.64.112]) by hermes.imsd.uni-mainz.de (EMWAC SMTPRS 0.83) with SMTP id ; Fri, 12 Apr 2002 08:55:28 +0200 Content-Type: text/plain; charset="iso-8859-15" From: Markus Wagner Organization: IMBEI To: pgsql-general@postgresql.org Subject: how to get more detailed error messages? Date: Fri, 12 Apr 2002 09:04:10 +0200 X-Mailer: KMail [version 1.2] Cc: pgsql-sql@postgresql.org MIME-Version: 1.0 Message-Id: <0204120904101G.28384@magnus> Content-Transfer-Encoding: 8bit X-Archive-Number: 200204/497 X-Sequence-Number: 23212 Hi, we have a union query over three select queries with some hundred lines of SQL code, created as a view. When executing the code we get an error message "ERROR: UNION types "text" and "int4" not matched" with only the line number of the terminating semicolon included. This is a problem that we have with many other sql things, too. The line number of the semicolon is the only thing we know. If we had the line number of the error itself we could save much time. Alternatively, if we had the name of the variables (in the case above) or a little quote of the problem area, we would have much less trouble. Isn't there a way to get the parser to talk more precisely??? Thank you very much, Markus Wagner