Implementing SQLDataSources and SQLDrivers about odbc HOT 3 CLOSED

stemmertech,

I am not sure I would like this change. I have no need for such code, but I 
don't know about others.

Why would you write this code? How would you use it?

I can see 2 problems with your proposal:
- I would have to maintain that code in the future;
- user code that rely on this functionality won't be able to compile with any 
other database/sql driver.

So this new code better be useful.

Alex

Even for us there's is only a very specific case where this would be used. Some 
of our windows users have difficulty correctly setting up and using an ODBC DSN 
(when using MSSQL servers). We would use this to inform them of problems (DSN 
names that do not exist or aren't visible to the program, not using the SQL 
native driver leading to a significant drop in performance).

This new code would not be useful at all for users only interacting with 
database/sql, and migrating to another odbc driver would be difficult indeed. I 
understand this might not be useful to most of the users of this package, but I 
already wrote the code so I thought I would just ask if there was any interest.

Joël

Sounds like a useful option for your need. But I don't see how it can be used 
in general. So the answer to your offer is no.

I am glad Go works for you otherwise.

Thank you, for your comments.

Alex