Hi Kyle,
Thanks for the really thorough response, it seems you know what you're on
about :-) I agree with you that it would likely be a foolish decision to
rely on undocumented behaviour, this will likely come back to bite me at
some point in the future.
I'm going to take all these ideas away
Hi,
I'm currently developing a web application using TurboGears which
makes use of sqlalchemy (0.4.6). Turbogears exposes a global 'session'
object, which is initialised as
scoped_session(sqlalchemy.orm.create_session()). E.g. each thread gets
its own session object.
Other web-accessible
As I can see, the turbogears way of creating the session as I
described above does not use a connection pool. First of all, am I
right to assume this? The default way is to create a new connection to
the database whenever a session object is instantiated this way?
the Session usually
Bobby Impollonia wrote:
Outerjoin takes a second argument which is the join condition. If you
want it to have multiple conditions, you can combine them into a
single condition using and_:
table1.outerjoin(table2, and_(table1.something == table2.something,
table1.somethingelse == somevalue))
Hi,
I use py2exe to package an app that uses SQLAlchemy through Elixir.
When running the app in a non-packaged way, it works. But executing
the exe gives me the following traceback:
Traceback (most recent call last):
File app.py, line 89, in module
File wx\_core.pyc, line 7912, in __init__
Raoul Snyman wrote:
Hi,
I'm writing a Pylons app, connecting to an existing oldish database,
and while connecting from my Mac desktop everything is fine, but when
I connect from our dev server, I get the following error:
LookupError: unknown encoding: latin1_swedish_ci
I've done some
On Jul 25, 2008, at 5:34 AM, Raoul Snyman wrote:
I'm writing a Pylons app, connecting to an existing oldish database,
and while connecting from my Mac desktop everything is fine, but when
I connect from our dev server, I get the following error:
LookupError: unknown encoding:
With lots of hints I was able to solve this problem. Thanks!
Traceback (most recent call last):
File app.py, line 89, in module
File wx\_core.pyc, line 7912, in __init__
File wx\_core.pyc, line 7487, in _BootstrapApp
File app.py, line 20, in OnInit
File frame.pyc, line 52, in
On Jul 25, 2008, at 8:23 AM, Bram Avontuur wrote:
As I can see, the turbogears way of creating the session as I
described above does not use a connection pool. First of all, am I
right to assume this? The default way is to create a new connection to
the database whenever a session object is
