Thread: small ODBC problem
Jaeho,Huh (dduma@personaldb.net) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description small ODBC problem Long Description In console, if I execute the multiple statements including with one error statement, then all statements will succeed exceptthe one error statement. ( Of courcse I didn't use the 'BEGIN WORK' ) But in ODBC, if I execute the multiple statements including with one error statement, then all of the statements will notsucceed. In other words, multiple statements are executed in transaction state in ODBC though without 'BEGIN WORK'. I think ODBC run should be the same with the console. Is it a bug? Sample Code In console INSERT INTO a (aa,bb) VALUES ('a','b');INSERT INTO a (aa,bb) VALUES ('a',3); ^ ^ | | success fail In ODBC INSERT INTO a (aa,bb) VALUES ('a','b');INSERT INTO a (aa,bb) VALUES ('a',3); -----------> ALL Fail. No file was uploaded with this report
pgsql-bugs@postgresql.org wrote: > > Jaeho,Huh (dduma@personaldb.net) reports a bug with a severity of 3 > The lower the number the more severe it is. > > Short Description > small ODBC problem > > Long Description > In console, if I execute the multiple statements including with one error statement, then all statements will succeed exceptthe one error statement. ( Of courcse I didn't use the 'BEGIN WORK' ) > > But in ODBC, if I execute the multiple statements including with one error statement, then all of the statements will notsucceed. In other words, multiple statements are executed in transaction state in ODBC though without 'BEGIN WORK'. > > I think ODBC run should be the same with the console. > > Is it a bug? > A multi-statements query is treated as one command. It's a spec of PostgreSQL though it's not well known. Psql separates it into multiple commands and call them one by one by itself. regards, Hiroshi Inoue