[cvsnt] Re: Audit DB: commitlog.sessionid is always 0

[Tony Hoyle]

Olaf Groeger wrote:
> Hmm, i'm not sure that i understood you. You suppose that the insert in
> sessionlog doesn't returns the correct id but 0, which causes the 0 in the
> successesive inserts into commitlog and historylog?

Basically, yes.  There's no standardised way in SQL of returning the id 
of the last insert... indeed some (Firebird) can't do it at all.  In 
ODBC you can use select @@identity but that needs to be supported by the 
underlying driver.  Most of the native drivers have a function that 
returns it.

> Olaf
> 
> P.S.: Just out of curiosity: Which (serious) databases doesn't support
> referential integrity?
> 
Lots of the 'simpler' databases... Everything is written so it'll run on 
the simplest databases available, which means no referential integrity, 
no stored procedures, no 'complex' joins, etc.  Ultimately it can be 
tweaked for performance on high-end databases later.

Tony