Python and DB support (was: Re: Is Python Dead?)

David LeBlanc whisper at oz.nospamnet
Fri Jul 6 15:59:17 EDT 2001


In article <mailman.994135925.11224.python-list at python.org>, rnd at onego.ru 
says...
> On 2 Jul 2001, David Bolen wrote:
> 
> >Roman Suzi <rnd at onego.ru> writes:
> >
> >> However, my collegues were not satisfied with it. One somplain was that in
> >> ASP/IIS it is "very easy" to receive a "recordset" from database and then
> >> apply it in different situations in the ASP-page, because recordset is an
> >> object and even subqueries could be made without quering DB again.
> >
> >Just curious, but did your colleagues try using Python's COM interface
> >to ADO to retrieve an actual recordset object that they could
> >manipulate the same in Python as in other ASP languages?
> 
> Aha! Now I could understand what is the brake of Python library
> development. Most of Python users are Windows users. And they
> have COM for whatever is in their system.
> 
> >At least under Windows, it would seem that having solid ODBC and COM
> >support should pretty much cover in Python anything you'd do elsewhere.
> >
> >On other environments, direct support for a particular database is
> >likely to be more desirable, as it's more typical in those
> >environments, but as you've noted, there's a plethora of support
> >modules for various databases - some at various levels.
> 
> We mostly have Linux servers, so COM+ADO is no option. The point was not
> to choose between Windows and Linux, ASP was choosen to serve particular
> purpose, for the database already implemented in Microsoft land.
> 
> >--
> >-- David
> 
> Sincerely yours, Roman Suzi
> 

If you don't mind spending $$, then COM and ASP are most definately an 
option on Unix. Check out ChiliASP (www.chilisoft.com ?). Even COM all by 
it's lonesome is available for Unix since ChiliSoft uses a COM library 
from a 3rd party supplier.

Dave LeBlanc



More information about the Python-list mailing list