Re: [sqlalchemy] Advice: Best practice for working with an existing database

2013-04-06 Thread Michael Bayer
On Apr 6, 2013, at 11:42 AM, Roberto Guerra uri...@gmail.com wrote: +1. I prefer classical mapping also. Much cleaner. Keeps persistence and business logic separate. the reason I ended up not agreeing with this is because mapping applies instrumentation to a class. Using a

Re: [sqlalchemy] Advice: Best practice for working with an existing database

2013-04-06 Thread Roberto Guerra
On Apr 6, 2013, at 11:42 AM, Roberto Guerra uri...@gmail.comjavascript: wrote: +1. I prefer classical mapping also. Much cleaner. Keeps persistence and business logic separate. the reason I ended up not agreeing with this is because mapping applies instrumentation to a

[sqlalchemy] Advice: Best practice for working with an existing database

2013-03-18 Thread Peter Herndon
Hi all, I'm new to SQLAlchemy, and looking for some advice on how to approach working with an existing database. The database will not be managed by Python, and I will need to maintain whatever library I write to keep up with the occasional schema change. I am looking to write a more-or-less