|
From: Maciej (M. B. <ma...@op...> - 2013-10-16 21:59:12
|
2013/10/16 Oleg Broytman <ph...@ph...> > > It does what I need, but it doesn't seem like it's what SQLObject > > developers intended. Do you have any recommendations? > > I don't. Do you want to propose an API? Or better a patch? Hey, thanks for the reply. I'm looking at the code right now, I need to look more carefully at the current structure before I can suggest an API or a patch. In general, I can see 4 possibilities: - when creating a connection, add an option to not cache that connection - add an option to clear / expire all the connections in the current cache - add an option to the close() method so it causes the connection (and the URI) to expire from the cache - there already is special handling for in-memory databases, so maybe add a little more special handling for them; for example free the memory on close(). This could potentially break existing applications, does SQLObject make any guarantees about in-memory databases? Maciej |
