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

In article <19970820012400.VAA27669@ladder01.news.aol.com>, SaTriGuy <satriguy@aol.com> writes >>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 Remember that with a correlated subquery a temporary table is created/dropped for each dominant row processed E.g. select x,y,z < tab1.x is here from tab1 where z in ( select q from tab1,tab2 where tab1.x = tab2.q) << and tab1.x is here hence << this is a correlated sub-query For several thousand rows being processed you get several thousand temporary tables created and dropped!! -- David Williams