Hi Carlo, The second option (modidyfing connect instead of adding a different function to the environment object) is better, as connect already takes different parameters depending on driver anyway.
The ODBC driver currently has no maintainer, so feel free if you want to adopt it (at least for this fix :-) ). -- Fabio Mascarenhas On Mon, Dec 28, 2009 at 7:26 AM, CARLO KOKOTH <[email protected]> wrote: > Hi, > > I wanted to use connection strings instead of DSN's for the ODBC driver. So > i made a trivial change to the sources and added driver_connect function, > and everything seems to work OK. > > There have been a few requests in the past to add this functionality (at > least that's what google told me when i tried to find out whether it's > already supported), and now I finally kicked myself to ask whether you would > care for a patch. > > If adding a second connect-like function would seem inappropriate / > inconsistent with other drivers, I'd try to rewrite connect so that it would > try to detect usage of connection string (would simply checking for a > semicolon in the string be ok ???), and use driver_connect as / if needed. > > I have only tried it under Win32 (and don't even know whether unixODBC and > friends support driver_connect), and might not be aware of other tight > spots, so if you'd be interested, any guidance as how to make it > multi-platform aware / correct would be welcome (which #define would be the > right one to check for, etc.). > > Cheers, > CK > _______________________________________________ > Kepler-Project mailing list > [email protected] > http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project > http://www.keplerproject.org/ > _______________________________________________ Kepler-Project mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
