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

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.
[Microsoft][ODBC Driver Manager] Function sequence error

But when the error comes from the driver(for e.g Teradata), I believe,
it has to take the form.
[Teradata][ODBC Teradata Driver][Teradata Database] Object 'tmp1' does
not exist. 

I verified the same against UNIX DataDirect driver manager. Providing
the same below

Using Microsoft DM
[Microsoft][ODBC Driver Manager] Function sequence error //driver
manager pointing out the error and hence it's name
[Teradata][ODBC Teradata Driver][Teradata Database] Object 'tmp1' does
not exist. //driver pointing out the error and hence it's name

Using DataDirect DM
[DataDirect][ODBC lib] Function sequence error  //driver manager
pointing out the error and hence it's name
[Teradata][ODBC Teradata Driver][Teradata Database] Object 'tmp1' does
not exist. //driver pointing out the error and hence it's name

Using unixODBC DM
[unixODBC][Driver Manager]Function sequence error //driver manager
pointing out the error and hence it's name
[unixODBC][Teradata][ODBC Teradata Driver][Teradata Database] Object
'tmp1' does not exist. //driver pointing out the error and hence it's
name, but driver manager is also included

This is what I see in ODBC Programmer's reference
----------------------------
If the source of an error or warning is a component itself, the
diagnostic message must explain this. Therefore, the text of messages
has two different formats. For errors and warnings that do not occur in
a data source, the diagnostic message must use this format:
	
[vendor-identifier][ODBC-component-identifier]component-supplied-text
For errors and warnings that occur in a data source, the diagnostic
message must use this format:
	
[vendor-identifier][ODBC-component-identifier][data-source-identifier]da
ta-source-supplied-text

----------------------------

I hope, I am not pestering you :)

Thanks,
Hemanth


-----Original Message-----
>
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
_______________________________________________
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