On Mar 3, 2008, at 11:23 AM, Michael Bayer wrote:
On Mar 3, 2008, at 11:56 AM, Patrick Hartling wrote:
hash(Works())
hash(Works2())
# Raises TypeError with Python 2.6 because Fails is deemed
unhashable.
hash(Fails())
Does anyone know of a workaround for this issue? So far,
At 04:04 PM 2/27/2008 -0500, Michael Bayer wrote:
do you have any interest in committing changes to the branch
yourself ? as long as the unit tests keep running whatever you'd want
is most likely fine with meotherwise I will at least experiment
with doing away with __mro__ searching and
the bug is that unregister_attribute() is not working, which the test
suite is using to remove and re-register new instrumentation:
class Foo(object):
pass
attributes.register_attribute(Foo, collection,
uselist=True, typecallable=set, useobject=True)
What is the proper connection string for sqlalchemy to support pool_recycle?
Is there a setting in mod_Wsgi to support this?
sqlachemy.dburi=mysql://username:[EMAIL PROTECTED]:3306/databasename ??
I found the following :
On Mar 3, 2008, at 9:17 PM, Lukasz Szybalski wrote:
What is the proper connection string for sqlalchemy to support
pool_recycle?
Is there a setting in mod_Wsgi to support this?
its a create_engine option, so its a keyword argument - i.e
create_engine(url, pool_recycle=3600).
I didnt
On Mon, Mar 3, 2008 at 8:26 PM, Michael Bayer [EMAIL PROTECTED] wrote:
On Mar 3, 2008, at 9:17 PM, Lukasz Szybalski wrote:
What is the proper connection string for sqlalchemy to support
pool_recycle?
Is there a setting in mod_Wsgi to support this?
its a create_engine option, so
On Mar 3, 2008, at 9:36 PM, Lukasz Szybalski wrote:
I'll add
sqlalchemy.pool_recycle = 3600 to my prod.cfg (turbogears)
How is the pool recycle going to affect performance?
used properly, pool recycle has a negligible effect on performance.
every X amount of seconds (which you should
