Re: ESQL/C transaction logging - outside a transaction?
Posted in 1997
Topics: Installation, Setup & Upgrades, Storage & Space Management, Connectivity: ESQL/C, 4GL & Embedded SQL, Transactions, Locking & Isolation
Dear All,
My 0.02c worth.
1. If the databse is mode ANSI then any statement starts an implicit
transaction, if just normal logging then only data modifying
statements start a transaction.
2. Correlated subqueries in some versions of Informix log the
creation/destruction of the temp tables required for the sub query. .
To avoid the above, use isoaltion set to dirty read, use temp dbspaces
and DBSPACETEMP so that temp tables are created in non-logging
dbspaces, or if an older version of Informix then upgrade. Or I
suppose re-write the query to not use correlated subqueries and create
temp tables explicitly with no log.
HTH,
Jason
On 20 Aug 1997 01:24:05 GMT, satriguy@aol.com (SaTriGuy) wrote:
>>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