dynamic relation prevents delete cascade from loading in existing items

[Mike Bayer]

the get_history(passive=False) needs to load in the full list of child elements and assign it to CollectionHistory.unchanged_items, so that a delete of the lead object detaches / cascades to the child items.

also verify that this is working OK with the recent lazy load change.

[Mike Bayer]

this was fixed as of version 0.4.2 (also is present in CHANGES there).

[Former user]

testcase for firebird

[Former user]

Doesn't work in 0.4.3 on Firebird. Attached testcase gives a "violation of FOREIGN KEY constraint".

[Former user]

Replying to guest:

Doesn't work in 0.4.3 on Firebird. Attached testcase gives a "violation of FOREIGN KEY constraint". Neither in 0.4.4.

[Mike Bayer]

confirmed the bug with postgres and fixed in 190436e58df15a994fd57699e00bbfdbcc0e1848, which is most likely the same issue experienced in firebird. CHANGES message for 0.4.2 was incorrect, "delete" cascade was not implemented, only "null out foreign keys" behavior for a non-cascaded delete.

thanks for locating the correct ticket and test case !

[Former user]

Replying to zzzeek:

confirmed the bug with postgres and fixed in 190436e58df15a994fd57699e00bbfdbcc0e1848, which is most likely the same issue experienced in firebird I can confirm the issue is fixed for firebird either. Thanks!

[Mike Bayer]

Removing milestone: 0.4.xx (automated comment)