hey mike,
Just to confirm - trunk fixes problem with deletion.
Additionally, I have removed the lazy loading condition and it
maintains the speed of the query.
Thanks again to the team,
Martin
On Dec 7, 4:14 pm, Michael Bayer [EMAIL PROTECTED] wrote:
hey martin -
this bug is fixed in
Hello again Michael,
Have read the documentation you referenced, but am still unsure how to
now delete a Tag without generating the following error: (Note - using
Postgres in production)
(IntegrityError) update or delete on tags violates foreign key
constraint employeesTags_tag_id_fkey on
On Dec 7, 2007, at 5:21 AM, Martin Pengelly-Phillips wrote:
Hello again Michael,
Have read the documentation you referenced, but am still unsure how to
now delete a Tag without generating the following error: (Note - using
Postgres in production)
(IntegrityError) update or delete on
hey Mike,
Thanks for the update - I'll try it out tomorrow.
Martin
p.s. Have I mentioned you guys provide the best support I have
encountered in a long time (including commercial products).
On Dec 7, 4:14 pm, Michael Bayer [EMAIL PROTECTED] wrote:
hey martin -
this bug is fixed in trunk
Thank you Michael - I had completely missed the backref full load.
On Dec 5, 5:27 pm, Michael Bayer [EMAIL PROTECTED] wrote:
hi martin -
the issue is that each Tag object contains a collection of 1000
employees on it, and when you make an assignment in the forwards
direction (i.e.
hi martin -
the issue is that each Tag object contains a collection of 1000
employees on it, and when you make an assignment in the forwards
direction (i.e. employee.tag.append(sometag)), the corresponding
reverse relation needs to be fully loaded and then updated according
to backref semantics.
