when issued a request for eConnMaxActiveConnection for
disconnected database instead of returning 1, can check
for an driver parameter in dbxdriver and return a
configured value instead of 1.
Logged In: YES
I had already thought of this when I wrote the driver.
You might have seen my recent comments about it in the
There are 2 problems:
1 - Bug in SqlExpr.pas calls eConnMaxActiveConnection
before connect. That's why I have to report 1 (worst case
scenario) if not yet connected.
2 - There is no way to add driver-specific parameters such
as we are suggesting. We would have to mis-use one of the
other parameters, and I really don't want to do this.
The real answer is for our driver to clone the connection
itself if the underlying database does not support multiple
statements per connection. Then it can always report 0
(that is, unlimited statements per connection), even if the
underlying database does not really support it.
Internally cloning the connection in this way will also
solve another problem, which is that if the user has
specified driver prompt (Database = ?) it re-displays the
ODBC connection dialog every time the Borland code tries to
clone the connection.
I have now released the change to internally clone
connections when eConnMaxConnection<>0.
This solves your problem, as described in my previous
You can download the new version from the CVS area.
When testing is complete, I will release the new version to
the download area
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.