reflection is not a fast process at all since it aims to be comprehensive.
The MetaData, Table and everything related is pickleable for the purpose of apps that want to cache the results of reflection in a file, to be pulled out later. On Jun 17, 2011, at 10:47 PM, Mark Erbaugh wrote: > Is there overhead associated with reflection? When SA is used in a stateless > web server, I think it would have to do the reflection every time a new page > is served. Is there a way to create and reuse a "snapshot" of the reflection > results. > > I guess what I'm asking is if I write manual code that specifies the db > layout is setting that up significantly quicker than using reflection, and if > so, is there some way to generate manual code from the reflection process? > > I'm working with an existing database rather than one specifically designed > for the application. > > Thanks, > Mark > > -- > 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. > -- 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.
