Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong file names and information at Install\HtmlHelp.* [ODBC120] #117

Closed
firebird-automations opened this issue Apr 10, 2011 · 7 comments
Closed

Comments

@firebird-automations
Copy link

Submitted by: @ibaseru

1. OdbcJdbc\Install\http://HtmlHelp.uk\html really contains UKRANIAN text, so it must be named http://HtmlHelp.ua, not .uk.

2. Examples in both http://HtmlHelp.uk and http://HtmlHelp.ru are given with the transation options
"SET TRANSACTION LOCAL\n"
"READ ONLY\n"
"ISOLATION LEVEL\n"
"READ COMMITTED NO RECORD_VERSION WAIT\n",

which is simulation of IB/FB API default read_committed options, but will confuse users or programmers "why read_committed mode give deadlocks on reading non-committed" data.
I recommend to avoid mentioning or specifying NO RECORD_VERSION in all places, in documentation and even in source code (there are such places), because normal read committed mode is RECORD_VERSION, wich is not reading uncommitted version and does not show deadlock on them.

See initial discussion at firebird-devel mailing list, the subject is
[Firebird-devel] ReadCommitted isolation mode in Firebird's drivers

I do not understand c++, so, I can't find what default transaction options are used in this driver for ANSI ReadCommitted mode. But I suspect that the problem is the same as for Firebird .Net provider - DNET337.

Commits: dd9ad29 95aa134

@firebird-automations
Copy link
Author

Commented by: @alexpotapchenko

1) uk is renamed to ua in cvs
2) ODBC driver 2.0 uses read-committed/rec-version by default. I have replaced "NO RECORD_VERSION" to "RECORD_VERSION" in help.

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.0.1 [ 10430 ]

Fix Version: 2.1 Beta [ 10410 ]

@firebird-automations
Copy link
Author

Commented by: @ibaseru

thanks, great (both 1 and 2).

@firebird-automations
Copy link
Author

Commented by: @ibaseru

Btw, Alexander. May I ask you to specify at Transactions.htm
supported ODBC isolation levels and sorresponding transaction parameters, as in
http://www.firebirdsql.org/dotnetfirebird/transaction-isolation-levels.html
?

Some people complains that transaction parameters in 2.0.0.148 is not expected or correct, as in document for .Net driver and in .Net driver itself.
Example:
http://www.sql.ru/forum/actualthread.aspx?tid=843450
(locks on reading non-committed data)

At first, none levels must have WAIT default option - everywhere must be NO WAIT, and WAIT must be optional.
Second, ReadCommitted isolation mode must have isc_dpb_rec_version option, not no_rec_version.

The problem is that driver developers seems that do not use their driver to develop software (do not use driver), and that's because transaction parameters are specified wrong way, than in other drivers or in direct access components like FIBPlus, IBX, etc.

@firebird-automations
Copy link
Author

Commented by: @alexpotapchenko

I have looked at the russian Transactions.htm, what is problem with current version?
Transaction parameters for ReadCommitted are fixed in 2.0.0.150.

@firebird-automations
Copy link
Author

Commented by: @ibaseru

I think there must be list of odbc isolation levels with corresponding Firebird transaction parameters. As in example document of .net driver.
Because people using odbc for connecting applications that will never specify Firebird transactions parameters directly.
Like this:
ODBC Firebird
READ_UNCOMMITTED - read committed, no rec version, no wait (this will give deadlock error on reading uncommitted data)
READ_COMMITTED - read committed, rec version, no wait
REPEATABLE_READ - concurrency, no wait
SERIALIZABLE - consistency, no wait

@firebird-automations
Copy link
Author

Modified by: @alexpotapchenko

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants