you'd need to send a fully self-contained code example that reproduces the
issue. the gists you have don't show any code.
On Oct 6, 2013, at 12:39 AM, Hyunjun Kim k...@hyunjun.kr wrote:
oh, i fixed the problem. your explanation was exactly right. most of tables
do not seem to have any
oh sorry. I thought the subject duplication shouldn't be in the mailing list.
I called configure_mappers() right before every query execution, but it does
not work still.
even one of erroneous class has only single column in table and has no foreign
keys or dynamical integration between any
oh, i fixed the problem. your explanation was exactly right. most of tables do
not seem to have any relation to errors so it was hard to find the error.
i have a dynamic module 'm' that is implemented to contain all ORM models for
convenience. one of relationship property referencing another
T_T
Hi, I am using SQLAlchemy 0.8.2 with PostgreSQL and having exactly same
problem.
I have a lot of table classes inherited declarative base and only some of
classes raise errors. (https://gist.github.com/yoloseem/d1c9b0f8d3cef6c196e4
)
Actually, even for same buggy classes, errors are
this is definitely not related to any issue from 2007. See what happens if
you call sqlalchemy.orm.configure_mappers() right before you emit that Query in
this particular test.the error indicates this particular class was not
present when the mappers post-configured themselves.
On Oct
Hi!
I made an aplication in my local machine but when I tried to do the same in
the server I had this problem:
Module Python expression view.indicators(), line 1, in expression
Module Products.odr.lugabe_db.browser.sql, line 23, in indicators
Module Products.odr.lugabe_db.query, line 48, in
