From: bill l. <bbi...@gm...> - 2010-10-15 23:31:07
|
Птн, 15 Окт 2010, GMS - Ulrich Hutter писал(а): > hi everybody, > > i changed to firebird 2.5 and the odbc driver 2.0.0.148 (Version 144 does not work on firebird 2.1 above) > Know i have a very big transaction problem. > I start a transaction in my application - so one row in my table is locked. > now i can not read with the ODBC driver this row - i always get a lock conflict 40001. > I just want to read, not to write. > of course i tried all setting in the odbc administrator. (read, nowait) > I want to print with crystal report, so i can not directly change the connection string. > > This worked very well with odbd 2.0.0.144 (i tested it know again) > > Because of this behaviour, i can not change to firebird 2.5 Not sure how did you set the isolation level. IIRC that cannot be set from odbcad32 panel, the read option only indicate one will not write data but it does not override transaction isolation. Firebird engine itself does not support read uncommitted. I'm not sure this changed in fb 2.5. You may try testing with odbc 148 with your original fb engine (2.1?) to confirm whether this is a problem of odbc driver. -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 |