Re: SQLExecDirect with SQL_ERROR dumps coreon suselinux-x8664

Yes, SQLGetFunction says SQLError is not being exported. Probably, this
has got something to do with our driver. I will take care of this.

Thanks Nick.. 

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Nick
Gorham
Sent: Wednesday, June 24, 2009 6:46 PM
To: Development issues and topics for unixODBC
Subject: Re: [unixODBC-dev] SQLExecDirect with SQL_ERROR dumps coreon
suselinux-x8664

G, Hemanth Kumar wrote:
>
> Hi Nick,
>
>       I have compiled unixODBC for suselinux-x8664.
> My odbc application dumps core when an incorrect sql statement is used

> in SQLExecDirect.
>
> SQLExecDirect(hstmt, (SQLCHAR *)"select abcd", SQL_NTS);
>

It looks like its trying to call SQLError in the driver, and I guess it
failed to extract a entry point for SQLError so the attempt to call
address 0.

The code tests to see if the driver exports SQLGetDiagField or
SQLGetDiagRec, and if it doesn't assumes that it must be ok to call
SQLError. IN this case, it seems as if none of the error functions are
exported by the driver.

I will look at adding a check to prevent the seg fault, but I would
check whats being exported and what SQLGetFunction is reporting.

--
Nick
_______________________________________________
unixODBC-dev mailing list
[email protected]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
_______________________________________________
unixODBC-dev mailing list
[email protected]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev