>
>
> I have your book and read your recomendations. At work on the
> other hand ODBC is not seen as the way to go we use ADO.
Things move on... if working with Microsoft databases then
ADO and COM interfaces make a lot of sense and will give
you all the latest features. I doubt there is a performance
benefit.
However, if want to get at Sybase/Oracle or a dozen other
database engines then you can almost alway find an ODBC driver.
I do a lot of cross-platform work for big corporates where we can
develop on a local windows box and run on Unix; Python's
consistent DB API makes this very easy.
> For Python I'm also reading up on ADO to see how it compares
> to the odbc approach.
>
> One thing I did not want to do was have to do sys admin to
> setup ODBC. With ADO I can pass it the access info from within
> my app.
Actually you can register ODBC data sources at run time
yourself; I cannot remember the API calls but have done it before.
So you can ship an app which needs no configuration. mxODBC
does not expose this AFAIK but it can be done with the windows
extensions.
> BArry
> p.s.
> Where in the U.K are you based?
London - Wimbledon
_______________________________________________
ActivePython mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/activepython
