[Info-ingres] FW: [Users] How to Log errors while executing ingres sql command

-----Original Message-----
From: users-bounces+pwhite= XXXX@XXXXX.COM  [mailto:users-bounces+pwhite= XXXX@XXXXX.COM ] On Behalf Of Ronald Jeninga
Sent: Monday, 20 February 2006 6:51 PM
To:  XXXX@XXXXX.COM 
Subject: Re: [Users] How to Log errors while executing ingres sql command

Hi,

use awk, like e.g. :

ronald@serval:~/eclipse_workspace/SDMS/src> sql sdmsdb2 < /tmp/x | awk '
E_US0845 Table 'table_does_not_exist' does not exist or is not owned by
    you.
    (Mon Feb 20 08:45:31 2006)

The /tmp/x script looks like

select * from table_does_not_exist;
\p\g

select count(*) from iitables;
\p\g


The main problem is not to catch the error messages, it is the transaction logic. So if your script tries to perform multi-statement transactions, you'll end up with an inconsistent database (if you are unlucky, and programmers better not count on their luck).

HTH,

Ronald


On 20 Feb 2006 10:25:50 +0530





independIT Integrative Technologies GmbH Sitz der Gesellschaft: Schrobenhausen HRB Neuburg B 1.521
Geschtsfrer:
  Dieter Stubler, Dipl. Inform. (FH)
  Ronald Jeninga, Diplom Mathematiker
_______________________________________________
Users mailing list
 XXXX@XXXXX.COM 
 http://www.**--****.com/ 

logic.
end up
not

Amen to that, brother.  sql is really just an alias for tm, and tm was never
designed for SQL.  It was designed for QUEL, a language in which transaction
boundaries are always explicitly identified.  Also unlike SQL, QUEL
implicitly rolls back any uncommitted transactions when tm (or any other
front-end) abruptly terminates--but that's another issue (it's actually
wrong behaviour required by the ANSI/ISO SQL standard).  Considering how
much sql/tm is used, someone really ought to spend some time adapting it to
properly support SQL.  (That is probably well within the ability of a
ba{*filter*}t tinkerer but I don't currently have time myself.)

At least in an SQL script is easy to tell what the flow-of-control is, so
rediscovering the transaction boundaries is relatively easy.  (Unlike
embedded SQL applications where one generally has only two choices: either
we know it's wrong, or at best(?!) we don't have a clue!  Not a good
situation.)

Roy Hann (rhann at rationalcommerce dot com)
Rational Commerce Ltd.
www.rationalcommerce.com
"Ingres development, tuning, and training experts"
Ingres Corporation Partner