SQLConnect problem

Hello,

The behaviour of SQLConnect has been changed since 3.51.06
We were using this version in combination with our application with no
problem but now when I updated to 3.51.11 I ran into problems.

I let the application create a user dsn with the database I want to
connect to. When this database does not exist the drivers correctly
returns the error that this database does not exist and the connection
is closed.
I then let the application reconnect to MySQL but now without a database
filled in the DSN.

With driver 3.51.06 the function SQlConnect runs ok and I am enable to
construct a query "CREATE DATABASE bla" and execute it.

With driver 3.51.11 (I also tried 3.51.10 with the same result) the
function fails because for some reason it uses the DSN name as database
name to connect to which obviously also does not exist.

Why did this behaviour changed like this?

How do I suppose to create a database now through ODBC if the SQLConnect
function fails?

Anybody?

--

Peter Lindeman
TPA traffic & parking automation bv

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: SQLConnect problem

Peter Lindeman wrote:
> Hello,
>
> The behaviour of SQLConnect has been changed since 3.51.06
> We were using this version in combination with our application with no
> problem but now when I updated to 3.51.11 I ran into problems.
>
> I let the application create a user dsn with the database I want to
> connect to. When this database does not exist the drivers correctly
> returns the error that this database does not exist and the connection
> is closed.
> I then let the application reconnect to MySQL but now without a database
> filled in the DSN.
>
> With driver 3.51.06 the function SQlConnect runs ok and I am enable to
> construct a query "CREATE DATABASE bla" and execute it.
>
> With driver 3.51.11 (I also tried 3.51.10 with the same result) the
> function fails because for some reason it uses the DSN name as database
> name to connect to which obviously also does not exist.

I also found 3.51.09 and this version is working ok.

--

Peter Lindeman
TPA traffic & parking automation bv

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: SQLConnect problem

Peter Lindeman wrote:

Nobody has noticed this behaviour and perhaps have a solution for it?

> Hello,
>
> The behaviour of SQLConnect has been changed since 3.51.06
> We were using this version in combination with our application with no
> problem but now when I updated to 3.51.11 I ran into problems.
>
> I let the application create a user dsn with the database I want to
> connect to. When this database does not exist the drivers correctly
> returns the error that this database does not exist and the connection
> is closed.
> I then let the application reconnect to MySQL but now without a database
> filled in the DSN.
>
> With driver 3.51.06 the function SQlConnect runs ok and I am enable to
> construct a query "CREATE DATABASE bla" and execute it.
>
> With driver 3.51.11 (I also tried 3.51.10 with the same result) the
> function fails because for some reason it uses the DSN name as database
> name to connect to which obviously also does not exist.
>
> Why did this behaviour changed like this?
>
> How do I suppose to create a database now through ODBC if the SQLConnect
> function fails?
>
> Anybody?
>


--

Peter Lindeman
TPA traffic & parking automation bv

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: SQLConnect problem

Peter Lindeman wrote:

>> The behaviour of SQLConnect has been changed since 3.51.06
>> We were using this version in combination with our application with no
>> problem but now when I updated to 3.51.11 I ran into problems.
>>
>> I let the application create a user dsn with the database I want to
>> connect to. When this database does not exist the drivers correctly
>> returns the error that this database does not exist and the connection
>> is closed.
>> I then let the application reconnect to MySQL but now without a
>> database filled in the DSN.
>>
>> With driver 3.51.06 the function SQlConnect runs ok and I am enable to
>> construct a query "CREATE DATABASE bla" and execute it.
>>
>> With driver 3.51.11 (I also tried 3.51.10 with the same result) the
>> function fails because for some reason it uses the DSN name as
>> database name to connect to which obviously also does not exist.
>
>
> I also found 3.51.09 and this version is working ok.

Nobody knows a solution for this problem?

Peter Lindeman



--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org