Wrong tpb parameters for standard transaction isolation modes -------------------------------------------------------------
Key: DNET-337 URL: http://tracker.firebirdsql.org/browse/DNET-337 Project: .NET Data provider Issue Type: Bug Components: ADO.NET Provider Reporter: kdv Assignee: Jiri Cincura Currently page http://www.firebirdsql.org/dotnetfirebird/transaction-isolation-levels.html and implementation of IsolationLevel.ReadUncommitted and IsolationLevel.ReadCommitted is not correct. IsolationLevel.ReadUncommitted have READ COMMITTED RECORD_VERSION tpb options, wich is wrong, because in the Firebird ReadUncommitted can be simulated only like this: read committed no record version no wait This will cause an error if transaction will attempt to read records with uncommitted versions. Even with this options it will be semi-ReadUncommitted, because Firebird will not allow to read uncommitted data in any way. Otherwise, IsolationLevel.ReadCommitted uses mentioned above "no record version" option, which does not allow to read only committed versions (error on nowait and lock on wait). Instead, ReadCommitted must use read committed record version no wait This tpb parameters exactly corresponds to the standard ReadCommitted isolation mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider