On Jun 22, 2:30 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > this is a very old and unused feature that I should probably remove in > 0.4. > > On Jun 22, 4:27 pm, d_henderson <[EMAIL PROTECTED]> wrote: > > > A call to sqlalchemy.engine.engine_descriptors() fails with this > > traceback:
I like the idea of a call which enumerates available engines. It's certainly easy to see if the module is installed, but a bit more difficult to see if it is supported There are at least 3 choices for Sql Server dbapi modules in Python, and another three in IronPython, each with different pros and cons. There are at least two, and possibly more, modules that will connect to an Oracle database. On a windows box, there are a number of independent python implementations: Python, Jython, IronPython, ActivePython, PortablePython, cygwin Python. Each of these could have a different suite of installed dbapi modules. I think we need all the help we can get to discover and diagnose the environment. I'd like to see engine_descriptors left in, documented more prominently, and perhaps even enhanced. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
