On Jun 22, 4:22 pm, d_henderson <[EMAIL PROTECTED]> wrote:
> Is it reasonable to make an option, similar to use_scope_identity, to
> optionally use my query in place of the information schema query?
> Should I maintain a local version of SQLAlchemy with this query, or
> would it be generally useful?
you should create a patchfile in unified diff format against the
mssql.py module, ensure that the unit test test/engine/reflection.py
passes when its in place, then submit a trac ticket, attaching the
patchfile and any additional test cases youve created. I have been
advocating against the usage of information_schema in general since
every DB implements the specifics of it differently (thereby rendering
any platform-independent gains impossible), but all with great
slowdowns in speed.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
