Brad Clements wrote:
Luís Bruno wrote:
def filter_app_factory(application, global_conf, dburi, **kw):
global_connect(dburi, **kw)
return application
Yeah, maybe. However in tracing global_connect down, it seems to go
through create_engine and then to ComposedSQLEngine and kwargs dies
there
On 30 May 2006 at 23:17, Luís Bruno wrote:
> def filter_app_factory(application, global_conf, dburi, **kw):
> global_connect(dburi, **kw)
> return application
>
Yeah, maybe. However in tracing global_connect down, it seems to go through
create_engine and then to ComposedSQLEngine and kwargs die
Brad Clements wrote:
Michael Bayer wrote:
this keeps the URLs completely consistent and provides a nice
separation of "db-specific" vs. "db-agnostic".
Yeah, but then there's no way I can use sqlalchemy in a generic and
non-database specific way via WSGI using PasteDeploy
Well, maybe I'm giv
On 30 May 2006 at 16:30, Michael Bayer wrote:
> usually additional params that are specific to a certain database
> implementation are passed through as keyword arguments to
> create_engine():
>
> this keeps the URLs completely consistent and provides a nice
> separation of "db-specific" vs. "db-
usually additional params that are specific to a certain database
implementation are passed through as keyword arguments to create_engine():
x = create_engine('driver://user:[EMAIL PROTECTED]/db', do_this=True,
do_that=False)
the **kwargs of create_engine are passed to the constructor of the Di
I am trying to figure out how to get extra engine specific params from the db
url.
What I'd like is a url object that populates the standard attributes:
self.drivername = drivername
self.username = username
self.password = password
self.host = host
self.po
6 matches
Mail list logo
