Le mercredi 11 f�vrier 2004, Schildberg, Steffen a �crit...
bonjour,
> No idea. May be the commit is missing?
dbmcli 7.5.0.8 is not on autocommit mode ?
I know that my sqlcli is not on autocommit mode, so I know I _must_ commit
when using sqlcli (nice tool indeed, but what about linkage with GNU
Readline for Linux ?)
I used this syntax with SapDB 7.4.3.27 when I loaded bad dbproc
to drop them, before reloading better versions. And it was working.
But not this time. That's the difference.
> why not use the Loader to drop your dbproc? May be this will
> resolve your problem and you have all your statements executed
> with only one tool. The Loader executes sql statements and
> loader statements. It only does NOT return result sets in case
> of sql statements.
sure, you're right.
But dbmcli with a sql_execute should drop the dbproc when saying 'OK'.
May be future dbmcli versions should get rid of sql features ?
I made a test:
login with dbmcli in database test and create a table (empty). logout.
login again and try to "select * from table": no table (no autocommit ?)
recreate the table and commit
logout
login again. The table exists ! I insert one row. Do not commit. logout
login again and "select * from table": here is the row (autocommited ?)
hypothesis:
some statements are autocommited and some not ?
--
jm
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
