List:MySQL ODBC« Previous MessageNext Message »
From:Peter Harvey Date:February 2 2002 3:40am
Subject:Re: SQLConnect
View as plain text  
Uncommenting the call to set_dbc_error() causes the error again. Also; 
when I tried the unixODBC isql it locked up my machine but when I try 
the unixODBC DataManager (a GUI ODBC browser) the app will crash before 
the machine.

Peter

BTW: Turning unixODBC Trace off did not correct the problem.

Peter Harvey wrote:

> Venu,
> 
> I am not sure why this happens but I can tell you that it just locked up 
> my workstation, after creating > 250,000 lines in my odbc trace, forcing 
> a cold-reboot.
> 
> Anyway; I commented out these calls to set_dbc_error() and 
> translate_error() and it seems to work. That is it fails to login and 
> then returns an error.
> 
> You may not be able to reproduce it because the mirror in unixODBC 
> (which I am using) may be different from what you are trying. Not sure.
> 
> I will look into it a bit more before moving on. I will let you know if 
> I find anything new. Who knows... it could also be a build issue... 
> threads or something.
> 
> Peter
> 
> 
>   /* socket[0] is always 0 if you are not under UNIX */
> printf( "[PAH][%s][%d]\n", __FILE__, __LINE__ );
>   if (!mysql_real_connect(&dbc->mysql,host,user,passwd[0] ? passwd : 0,
>               database, port_nr,
>               socket[0] ? socket: NullS,
>               (uint) client_flag))
>   {
> printf( "[PAH][%s][%d]\n", __FILE__, __LINE__ );
> /*
> set_dbc_error(dbc, "S1000", mysql_error(&dbc->mysql),
>           mysql_errno(&dbc->mysql));
>     translate_error(dbc->error.sqlstate,"S1000",mysql_errno(&dbc->mysql));
> */
>     DBUG_RETURN(SQL_ERROR);
>   }
> printf( "[PAH][%s][%d]\n", __FILE__, __LINE__ );
> 
> 
> Venu wrote:
> 
>> Peter,
>>
>>
>>> -----Original Message-----
>>> From: Peter Harvey [mailto:pharvey@stripped]
>>> Sent: Friday, February 01, 2002 4:50 PM
>>> To: myodbc
>>> Subject: SQLConnect
>>>
>>>
>>> Seems the SQLConnect spins when a login fails. I have to assume someone
>>> has alreay noted this.
>>>
>>
>> No, I couldn't able see or reproduce it. Could you please
>> how to reproduce this ?
>>
>> Regards, Venu
>> -- 
>>
>>
>>> An ODBC trace shows the DIAG message repeating until the app dies.
>>>
>>>
>>> [ODBC][11941][SQLConnect.c][2390]
>>>                 Entry:
>>>                         Connection = 0x80bd558
>>>                         Server Name = [myodbc3-test][length = 12 
>>> (SQL_NTS)]
>>>                         User Name = [pharvey][length = 7 (SQL_NTS)]
>>>                         Authentication = [][length = 0 (SQL_NTS)]
>>>                 DIAG [S1000] [MySQL][ODBC 3.51 Driver]Access denied for
>>> user: 'pharvey@stripped' (Using password: NO)
>>>
>>>                 DIAG [S1000] [MySQL][ODBC 3.51 Driver]Access denied for
>>> user: 'pharvey@stripped' (Using password: NO)
>>>
>>>
>>>
>>> * MyODBC 3.5 (as found in unixODBC CVS today).
>>> * mysql  Ver 11.12 Distrib 3.23.33, for pc-linux-gnu (i686)
>>>
>>> Peter
>>>
>>> BTW: The old driver seems to work just fine.
>>>
>>
>>
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
> posting. To request this thread, e-mail myodbc-thread4742@stripped
> 
> To unsubscribe, send a message to the address shown in the
> List-Unsubscribe header of this message. If you cannot see it,
> e-mail myodbc-unsubscribe@stripped instead.
> 
> 
> 


Thread
SQLConnectPeter Harvey2 Feb
  • RE: SQLConnectVenu2 Feb
    • Re: SQLConnectPeter Harvey2 Feb
    • Re: SQLConnectPeter Harvey2 Feb
      • RE: SQLConnectVenu2 Feb