Hello,
I'm using SQLAlchemy 0.3.4. I'm having the following problem when trying
to delete an object:
client = model.Client.get(1)
client
mp.models.clients.Client object at 0x1088210
client.delete()
Traceback (most recent call last):
File console, line 1, in ?
File
okay, how would u do something like
(person.address1.country.name == 'France' or
person.address2.country.name == 'Germany')
note there are 2 different address1 and address2 fields of the person.
and, how would this be like:
(person.address1.country.name == 'France' or
person.company.name
On Jan 26, 5:49 pm, Michael Bayer [EMAIL PROTECTED] wrote:
doing away with the __del__() thing ? what would we gain by
removing the __del__() call ?one thing I should do is insure ORM
etc. do not rely upon __del__() (which they shouldnt, although I just
tested with the AssertionPool
Damjan schrieb:
Now, creating pages and then adding tags to them like so:
p1.tags.append(Tag('test'))
p2.tags.append(Tag('test'))
will actually create two 'test' tags in the database...
Have a look at my tagging tutorial at
http://paddyland.serveblog.net/article/16#updating-tags
Although
Employee points to Dept and Dept points to Director; Director
inherits Employee. no other references.
thats not the test case im talking about, you gave me just A and
B with B point to A (which is A pointing to A).
that right, i found another case giving the same error, and thought it
Mike,
On a side note, do u have any ideas about supporting stored procedures
in some way? Be it just knowing about them and maybe calling them, or
on the other end, generating them?
IMO they are _some_ way to hide some of those session.queries...
Although i'm just extrapolating my own vision
Can we invent some practical rule about what cannot (or should not)
be lazy?
sorry, what cannot (or should not) be _eager_
a) self-reference and inheritance between pointing and pointed, in
any direction
b) anything else ??
--~--~-~--~~~---~--~~
You
