After some tests with weak_identity_map=False see that the source of
the ORM queries for attributes is not related to garbage collection.
They aren't issued if query caching is off, so the problem is related
to caching.
When I write:
theme = session.query(Theme).cache_key().get(..) # gets
On Nov 8, 2009, at 6:48 AM, James wrote:
On Nov 7, 5:28 pm, Michael Bayer mike...@zzzcomputing.com wrote:
the most obvious cause would be that two different engines are being
used, since sqlite memory databases are local only to a single
connection.
Thanks for this pointer Michael!
I
On Nov 7, 2009, at 6:03 PM, Adam Dziendziel wrote:
Hi,
I am trying to use the query caching solution described here:
http://svn.sqlalchemy.org/sqlalchemy/trunk/examples/query_caching/per_session.py
In most cases it works, the returned records are cached, I store them
in a LRU cache
On Nov 8, 2009, at 6:21 AM, Adam Dziendziel wrote:
After some tests with weak_identity_map=False see that the source of
the ORM queries for attributes is not related to garbage collection.
They aren't issued if query caching is off, so the problem is related
to caching.
When I write:
Hi , i am sorry for my english, i am trying ti make a Server/Client
app. Until now client-gtk mapped the db and spoked directly with the
db ( sqlite and postgresql atm) . I wrote a small wsgi server based
on werkzeug, and it basically make the same thing of the client-gtk
but in pure web style.
On Nov 6, 2009, at 7:53 PM, David Gardner wrote:
CREATE TABLE task (
name text NOT NULL,
asset text NOT NULL,
parent_asset text,
more columns
CONSTRAINT task_PK PRIMARY KEY (asset, name),
CONSTRAINT task_parent_FK FOREIGN KEY (parent_asset, name)
REFERENCES task (asset, name)
Something like this? The association table is declared in the relationships,
but never referenced when creating or accessing objects.
class Assoc(Base):
__tablename__ = 'assoc'
parent = Column(Integer, ForeignKey('m_to_n.id'), primary_key=True)
child = Column(Integer,
