You can reflect once, then cache the metadata (e.g. pickle it) then I think you can use autoload with usexisting
On Apr 30, 12:13 am, Kuze <kuze.to...@gmail.com> wrote: > I'm aware SQLAlchemy provides a comprehensive package for creating > database objects (tables, indexes, etc.) with a simple `create_all` > but I'm finding for my purpose, I'd rather manage object creation with > old fashion SQL scripts due to requirements both during development > and in production. > > I'm also aware of `reflection` capability provided. However, it'd be > hitting the database with a query to grab the necessary data points > for generating the schema. For production, hitting the db when using > reflection does not sound compelling. > > With my assumption that reflection isn't for production. What's the > bare minimum required for data access? > > Note: I'll be using declaritive extension for any required > definitions. I'll be making use of the ORM (Query, Events, etc). I'll > be using Mixins and Metaclasses where needed to cut down boilerplate > code. > > I've a hunch that perhaps it's only indexes which would not need to be > defined with SQLAlchemy cause they need not be created, but willing to > see what others have to add. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
