On Wed, Feb 22, 2012 at 5:51 PM, Claudio Freire <klaussfre...@gmail.com> wrote: > Such caches, for instance, are better made limited in lifespan (say, > giving them a finite lifetime, making them expire, actively cleaning > them from time to time). Structures that are truly required to be > eternal are better populated at load time, early in the program's > lifecycle. In my backend, for instance, queries are precompiled at > startup, to make sure they have lower memory addresses. This has > mostly solved SQLA-related memory fragmentation issues for me.
One source of trouble I've had here, is the inability to use bind parameters inside .in_(...). Queries that accept variable lists, thus, I had to "precompile to string", and replace the inside of the condition by string interpolation. Ugly hack, but it served me well. -- 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.
