wow that sucks does the warnings module document that ? we'd have to change that warning immediately.
On Jun 7, 2010, at 9:09 AM, nekto0n wrote: > Hi there! > Interesting feature was discovered. When you supply queries with non- > unicode values you get this: > Unicode type received non-unicode bind param value > 'ya37esbr24qhlu9kojf5z1x6m8gvinc0' > > All warnings after being emitted go into the warning registry in order > to be able to ignore them in future. Registy is a dict, with key: > key = (text, category, lineno) > > "text" is always different as you can see, so eventually - every > single warnings ends up being held in the registry, causing memory > leak. Wasn't sure if it's a bug or just nice feature - decided to > write here. Maybe it should be better to put 'value' somewhere else, > not in actual text? > > -- > 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.