Just to rephrase everyone else's "It doesn't matter" response: Many ORMs out there REQUIRE the database be built by the ORM or designed by the ORM. This is because the ORM stores and accesses data in a very particular manner -- so tables and columns must adhere to certain naming conventions, and tables must have certain types of primary keys or cross-table joins. The ORM ends up designing the database to be what is easiest/best for the ORM.
SqlAlchemy is the exact opposite. It lets you map ORM classes to new or existing database structures of your choice. You can map virtually any legacy database you have onto a set of SqlAlchemy ORM classes. You're fully able to define the table and column names, their content types, and their relations across the database. You have nearly no restrictions. [ I've never encountered a restriction, but there could be. ] You can design the database to be what is best for your application logic or data warehousing needs. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
