On Mar 14, 2011, at 6:14 PM, Ajay wrote:
Thanks Mike for your quick response.
I removed the zope.sqlalchemy extension and I am no longer getting the
zope error.
Since we are using a scoped_session, we don't think it's a threading
issue although we are running in a multi-threaded env.
Hi
I'm not sure how exactly to describe my problem, or what parts of code
to submit in support of this query. I have spent time Googling but,
since I'm not sure how to define the problem, I'm not sure what to
look for either. Sorry.
I have a feeling that my problem, somehow, relates to sessions,
-Original Message-
From: sqlalchemy@googlegroups.com [mailto:sqlalchemy@googlegroups.com]
On Behalf Of jln
Sent: 15 March 2011 16:37
To: sqlalchemy
Subject: [sqlalchemy] In-memory object duplication
[SNIP]
statuses = OneToMany('DocumentStatus', inverse='doc', cascade='all,
I'm wondering if there is a way to define a relationship without
creating an associated foreign key constraint in the database. It
seems like relationship() requires me to define a foreign key, and
that in turn automatically creates a foreign key constraint. I'm
currently using the declarative
On Mar 15, 2011, at 11:17 AM, nospam wrote:
I haven't been able to reproduce this issue and only saw it once. Any
ideas? Looks like the list of keys is out of sync w/ the dict in the
OrderedDict ... fyi, I don't have a column or property name
items_type. However, I do have an inheritence
The foreign key and join condition can be specified as part of the relation
definition without having the foreign key existing in the database
class User(Base):
__tablename__ = 'users'
logon = Column(String(10), primary_key=True)
group_id = Column(Integer)
class Group(Base):
