Antoine Pitrou wrote: > Le mercredi 27 janvier 2010 à 12:31 -0500, Michael Bayer a écrit : >> >> Or, we can generate the compiled() object, which contains the SQL string >> as well as a lot of important metadata about the statement used when >> fetching results. But this is not possible without access to a dialect >> and changes for every dialect - so we can key the string off of the >> current dialect in a dictionary. But another super edge case, some >> inexperienced users create new engines on every request of their >> application - the dictionary would grow and they'd say we have a memory >> leak (this has actually happened). > > You could use a weak key dictionary, which would remove the entry as > soon as all strong references to the dialect disappear.
my resistance with WKDs is that they're expensive compared to regular dicts. It means creating WKDs and weakrefs on every query, which will almost never be used. > > > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@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 sqlalch...@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.
