On 6/3/07, Mike Orr <[EMAIL PROTECTED]> wrote:
> There's also a get_engine_args() function which Michael didn't say
> much about but it's going to be a large percentage of the code. It's
> not just a matter of "sqlalchemy.dburi". There's also
> "sqlalchemy.pool_recycle" which is critical for MySQL, as well as the
> other engine options (or at least the scalar ones). It will also
> scale to multiple engines along the lines of
> "sqlalchemy.engine_key.dburi". This code is very Pylons specific, or
> at least it is until other frameworks/applications start using the
> same config file format.
By the way, I'm hoping to get a higher-level config-parsing function
or two into Pylons as part of this. Both SAContext and Buffet need to
read multiple keys with a common prefix and convert int/boolean
values, and perhaps recognize a subkey in between
("sqlalchemy.engine2.dburi"). This shouldn't have to be reinvented in
every library and user application, it should be part of Pylons or
ideally Paste.
By the way, what's the official home of CONFIG? paste.deploy.CONFIG?
paste.deploy.config.CONFIG? paste.config.CONFIG? I thought
paste.deploy.CONFIG was the current recommendation, put
pylons.util.config_get() thinks it's paste.config.CONFIG. But how can
CONFIG be a paste.config thing if it's part of PasteDeploy and not
Paste?
--
Mike Orr <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
