Re: ESQL/C transaction logging - outside a transaction?

>modification. Can anyone tell me why >transactions are being created when we never even begin a transaction to >start with and does anyone know whether there's a way to turn this stuff >off for particular apps and/or ESQL/C functions? Thanks. > > If the database is a logging database, then there is an implicit transaction arround every command so that individual transactions can be rolled back. Also, disk allocation/deallocations are always logged, even with unlogged databases. Finally, any dml statements (i.e. create table, etc) will be logged. Probably the best thing to do to figure out what is being logged is to dump the log files via onlog (tblog). Madison Pruet