On Tue, Apr 22, 2008 at 10:26 AM, Nick Murdoch <[EMAIL PROTECTED]> wrote:
> The difference to me is that SQLAlchemy requires you to know how SQL works > in much greater depth, /and/ to learn how SQLAlchemy interfaces with it > all, before you can start using it. I'm not a DB expert, and I like how > SQLObject doesn't bother me with a lot of the details before getting on > with it. i think this also holds the other way round. if you already know how sql works, you might be better off with sqlalchemy. in my case, i already had a legacy db with composite, non-integer foreign keys, and changing the schema to make it work with sqlobject didn't really appeal to me. robert > > > Nick > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > sqlobject-discuss mailing list > sqlobject-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
