>I dont't compare firebird to ms sql, and I surley don't give up.
> If the database isnt't able to handle such problems one has to invent a
> workaround. It's obviously a bug that -although the docu says that read
> committed DOES read only committed records- it doesn't and exits by
> throwing an exception on an uncommitted record without reading the next
> committed ones..unique behaviour..
>

That's wrong! What is normally does is read the last committed version of
that
record. Writers don't block readers.


I don't get your description of:
I just want the 2nd transaction to "overread" pending changes from others

What does that mean? Do you want to read the data that's available or do you
want that reader to read the current uncommitted data? (dirty read)


With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!

Database questions? Check the forum:
http://www.databasedevelopmentforum.com