I'm currently trying to get ecpg more in line with the backends parser.
Doing so I found ecpg accepts a syntax the backend doesn't. It's 'commit
work release' which is accepted for compatibility with Oracle. How about
allowing this in the backend, too?

Michael
-- 
Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
meskes@debian.org                      | 52146 Wuerselen
Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10

Fri, 13 Mar 1998 11:22:08 +0100 (CET)
Michael Meskes <meskes@topsystem.de>
Keyword
> I'm currently trying to get ecpg more in line with the backends
> parser. Doing so I found ecpg accepts a syntax the backend doesn't.
> It's 'commit work release' which is accepted for compatibility with
> Oracle. How about allowing this in the backend, too?

I don't want to sound too fussy here, but does this statement provide
any functionality missing from the SQL92 syntax 'commit [work]'? If not,
then perhaps Oracle users could start writing portable code if they
cared to?

                       - Tom

Fri, 13 Mar 1998 15:04:21 +0000
"Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Re: [HACKERS] Keyword