Re: Regarding error messages coming from the driver(and not from the driver manager)

No, there is nothing such, that would be gained by the change. We got
mismatches from our ODBC application and just wanted to confirm if this
has to be taken care of, by the driver manager.
I would now proceed with changing our application itself.

Thanks,
Hemanth. 

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Nick
Gorham
Sent: Friday, June 05, 2009 2:40 PM
To: Development issues and topics for unixODBC
Subject: Re: [unixODBC-dev] Regarding error messages coming from the
driver(and not from the driver manager)

G, Hemanth Kumar wrote:
>
> Nick,
>
> I might not be clear enough in representing the issue in my earlier 
> mail. Let me try to be more clear this time..
>
> Even Microsoft driver manager appends its vendor's name, but only for 
> errors that come from driver manager, and not from the driver.
>
Yes, I see that, but the point I was making is if I remove the
[unixODBC] and I get a report of the following error

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

There is no way to verify that the error involved unixODBC in any way. 
Its a matter of self preservation instead of strict adherence to the
spec in this case.

Its a simple thing to change, but it would be nice to hear what would be
gained by the change, I have said what would be lost...

--
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