Many users asked to switch from SQLObject to SQLAlchemy. Ah! You puny humans with such low-level dreams! ;-)
Ok... now that I've insulted my user-base, I've an announce: in the last 2 days I played with SQLAlchemy, without any serious intentions, but... surprise! It's not that difficult. And there's more: my plan is to support BOTH SQLObject and SQLAlchemy :-) I have a (mostly) working prototype: to limit the changes in the current code I've introduced an adapter to make SQLAlchemy behave like SQLObject (limited to our needs: a complete adapter is beyond my scope and won't be really useful). There's a little more black magic than I like, but lets call the code "clever" and not "a freaking mess", please. :-) Performances seems fine (for both inserting and reading), and I think I'll be ready to commit the first version to the CVS within the week. The problem is that I know next to nothing of the SQLAlchemy internals, and many things make me wonder... so the code will be full of XXX/TODO/FIXME/BLAMEITONSOCIETY notices. If someone with a little SQLAlchemy experience wants to help... Stay tuned, -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
