[SQLObject] Odd __connection__ problem
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Bruno T. <bt...@as...> - 2004-02-04 23:28:46
|
Hi there I'm going through an odd problem while getting connected to a databse within a class context. My code has the usual call: __connection__ =3D PostgresConnection(... the call is made in the module context and then every class that inherits SQLObject within the module has access to the connection and is able to query the database. This is for the development environment. In the production environment this isn't working. Although __connection__ is a valid database connection, objects created from that module classes cannot access the database. If I replace the call to __connection__ in the module context to a call like: _connection =3D PostgresConnection(... in the class __init__ method, then it works fine. I guess this is due to some mismatch between the configuration of the two environments, so far I have checked for python version (running 2.2.1 in both) and SQLObject version (both match, CVS latest) and I couldn't find anything. Can anyone point me a possible reason for this to happen? Where else to look for the problem? Thank you, []'s Bruno Trevisan bt...@as... |=3D| Async Open Source |=3D| D. Alexandrina, 253= 4 http://www.async.com.br/ |=3D| +55 16 261-2331 |=3D| 13566-290 |=3D| +55 16 9781-8717 |=3D| S=E3o Carlos, SP, B= rasil |