[unixODBC-dev] Regarding error messages coming from the driver..

Nick Gorham nick at lurcher.org
Thu Jun 4 13:09:57 BST 2009


G, Hemanth Kumar wrote:
>
> Hi Nick,
>
>       If the error comes from the driver, ideally it should take the 
> form..
> *[*/vendor-identifier/*][*/ODBC-component-identifier/*][*/data-source-identifier/*]*/data-source-supplied-text/ 
>
>
> For example, when selected from a non-existent table 'tmp1' from 
> Teradata datasource, Microsoft DM returns..
> [Teradata][ODBC Teradata Driver][Teradata Database] Object 'tmp1' does 
> not exist.
>
> Using unixODBC DM, the error message takes the form
> [unixODBC][Teradata][ODBC Teradata Driver][Teradata Database] Object 
> 'tmp1' does not exist.
>
> I suppose, [unixODBC] not be appended for errors coming from the driver.
> Correct me if I'm wrong!
>
> Thanks,
> Hemanth.
>
Yes, you are correct, but MS doesn't have the situation where there are 
other driver managers that could be in use, and apps that may be 
directly linked to drivers.

if I got a error report that was along the line of

"Your crappy unixODBC has reported

[Teradata][ODBC Teradata Driver][Teradata Database] Object 'tmp1' does 
not exist.

You need to fix it"

I could spend the next three days looking for a problem that in fact 
didn't involve unixODBC at all.

-- 
Nick


More information about the unixODBC-dev mailing list