On May 30, 2006, at 8:55 PM, Brad Clements wrote:
However I really want to change this so that url.py can parse out
extra engine
specific params.
ok what do you want here, dbengine://user:[EMAIL PROTECTED]:port/database?
opt=val&opt=val ? as long as its good with RFC1738. did you send me
a patch ? i lost track today. also how do you want to approach name
conflicts between databases ? do you want to prefix each name with
the drivername ? otherwise those URLs are still not agnostic.
A lot of tests fail, but they seem to have nothing to do with the
engine under test.
It would be helpful to know which tests were "in-progress" in the
trunk and which
were are supposed to work..
all 273 tests in the trunk at the moment pass on mysql, postgres, and
sqlite. tests that arent supported for a certain DB (like sequences
for mysql) have an "unsupported" decorator for that database, so they
pass too. so for any test, if for example 'sqlite' is not marked
as unsupported, then that test passes on sqlite. if not, then
something weird is going on, maybe your version of sqlite or
something about the windows environment (i havent run the tests on
windows in many weeks, perhaps its time to do that).
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
