Truncate with foreign key checks about pynonymizer HOT 7 CLOSED

@jerometwell the new table strategy works as expected / described.

from pynonymizer.

Hi! There is already a truncate table strategy, does this work for you?

https://github.com/jerometwell/pynonymizer/blob/master/doc/strategyfiles.md#table-strategy-truncate

from pynonymizer.

If i understand what you're trying to achieve ( cascading delete) then TRUNCATE won't work anyway.
IIRC truncate isn't suitable for tables with foreign keys.
You'd need a DELETE statement. Is this a feature you need?

As a workaround, you could add this as a before script:

scripts:
  before:
    - DELETE FROM table;

from pynonymizer.

@jerometwell yes you are correct, TRUNCATE doesn't actually work with foreign keys. The before script works, but an official table strategy would be more handy I think.

from pynonymizer.

@TitanNano in this scenario, would you have foreign key checks with CASCADE enabled? or were you implying that pynonymizer should do discovery also?

I'm just writing documentation and i want to be sure on the use-case.

I've started PR #23 for this issue. If you could take a look at the implementation I'd appreciate a second pair of eyes.

from pynonymizer.

@jerometwell yes CASCADE is enabled in our scenario. I will have a look at your WIP.

from pynonymizer.

This change has been merged into master and should go out with v1.13.0 - please test and report back if you can!

from pynonymizer.