Re: Beaker ext.database config

2007-10-28 Thread Ben Bangert
On Oct 27, 2007, at 3:57 AM, Robert Ian Smit wrote: During the upgrade to the current version of Pylons (0.9.6.1) and Beaker (0.8) db-based session and cache handling broke. The beaker config options are passed on to the create_engine call from sqlalchemy which raises an exception. The db

Re: Beaker ext.database config

2007-10-28 Thread Robert Ian Smit
During the upgrade to the current version of Pylons (0.9.6.1) and Beaker (0.8) db-based session and cache handling broke. I had thought that just url should be enough, however, I apparently missed enforcing some consistency in it. So, if you're using SQLAlchemy 0.3, the .url arg is

Re: Beaker ext.database config

2007-10-28 Thread Ben Bangert
On Oct 28, 2007, at 5:22 AM, Robert Ian Smit wrote: def load_environment(global_conf, app_conf): Configure the Pylons environment via the ``pylons.config`` object # The beaker code expects a class while the config option is # a string containing the name of the class. # If we

Re: Beaker ext.database config

2007-10-28 Thread Robert Ian Smit
On Oct 28, 5:49 pm, Ben Bangert [EMAIL PROTECTED] wrote: Why do you need to set the namespace class like that? You can't do: beaker.cache.sa.url = etc. In the ini file? My configuration was using namespace_class instead of type. Maybe there used to be a good reason for doing that,

Beaker ext.database config

2007-10-27 Thread Robert Ian Smit
During the upgrade to the current version of Pylons (0.9.6.1) and Beaker (0.8) db-based session and cache handling broke. The beaker config options are passed on to the create_engine call from sqlalchemy which raises an exception. For now I patched beaker.ext.database so that sa_opts is an