I originally would've stayed on a stable version, except, it was bugged mainly for oracle usage, so I *had* to move to the newer versions.
And don't you darn shove the "you lousy slack" up my arse. Do you have *any* idea how hard it is to isolate a specific mal-behaving combination in a huge model, extract and rewrite it so I can post it here? And I didn't do one or two of those! No Michael has no darn obligation, but the fact is that there is *no* other usable ORM for oracle in python, and wouldn't there be one, strategically my whole development would now be java and not python, which for multiple reasons I don't want, I'm sure you can empathize. But when you want me to stop thinking of testcases and just simply complain that things are broken without providing a test-program, just tell me. Quoting dmiller <[EMAIL PROTECTED]>: > Exactly! And don't complain about bugs on the bleeding edge. If you > need stability pick a revision and stick with it. Then devote time to > upgrade when you decide you need newer features. If you need the > newest features all the time deal with the fact that you'll be using > alpha-quality code, which means you'll be spending a lot of your time > making those new features stable. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
