Subject | Re: [IBO] Firebird 1.0 - RC1 & IBO |
---|---|
Author | Jason Wharton |
Post date | 2001-11-19T16:55:50Z |
What we have here in my opinion is a change made to the file access mode of
opening a database conflicting with the other ancillary operations which
have in the past depended on the shared file mode so that they can do what
they need to do with the file at the same time. By opening the file in an
exclusive mode, now other operations that previously worked are no longer
granted the access they need to do their job. This is purely a Firebird
issue.
The solution I propose is for the single server process to consolidate all
requests against a particular database to be handled through the same
connection instead of allowing a non-exclusive free-for-all against the
database file. I also think the server should let go of a database file
handle if there is no active connection to it.
In short, they have a good start to fix the bug but they need to finish up
the collateral effects as well.
Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
opening a database conflicting with the other ancillary operations which
have in the past depended on the shared file mode so that they can do what
they need to do with the file at the same time. By opening the file in an
exclusive mode, now other operations that previously worked are no longer
granted the access they need to do their job. This is purely a Firebird
issue.
The solution I propose is for the single server process to consolidate all
requests against a particular database to be handled through the same
connection instead of allowing a non-exclusive free-for-all against the
database file. I also think the server should let go of a database file
handle if there is no active connection to it.
In short, they have a good start to fix the bug but they need to finish up
the collateral effects as well.
Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com