On 1/5/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
yeah see, thats exactly the kind of thing i dont want SA's ORM to get
into, because its really thorny..updating the relationship on all child
objects. at the very least, it requires loading them all in, cascading
the change, etc. it gets prett
Arnar Birgisson wrote:
Now, what I really wanted to do is to write a method on my class that
takes care of changing it's primary key (or part of it, at least) and
cascade the change down to the children of that entity. Would that be
possible while keeping the process transparent to the caller,
On 1/4/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
Arnar Birgisson wrote:
> On 1/3/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
> > yeah that would be why. SA's ORM has no ability to update primary key
> > columns from their original valueyoull have to update it yourself,
> > or copy the
Arnar Birgisson wrote:
On 1/3/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
> yeah that would be why. SA's ORM has no ability to update primary key
> columns from their original valueyoull have to update it yourself,
> or copy the object instance to a new one, etc. (or not make that col a
On 1/3/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
yeah that would be why. SA's ORM has no ability to update primary key
columns from their original valueyoull have to update it yourself,
or copy the object instance to a new one, etc. (or not make that col a
primary key)
Ok thanks. Is
yeah that would be why. SA's ORM has no ability to update primary key
columns from their original valueyoull have to update it yourself,
or copy the object instance to a new one, etc. (or not make that col a
primary key)
--~--~-~--~~~---~--~~
You received
