I am running it with clone() before delete() and so far, it hasn't thrown any errors but I don't know for sure that the scenario which can cause this has happened yet. I will see if I can find one in my local environment to cause the issue.
Brian On Aug 16, 5:03 pm, Mark Mandel <[email protected]> wrote: > What happens if you try the clone? > > Honestly, Transfer was built with this sort of referential failure was an > non-expected error, and can (apparently) cause issues. > > I think the easiest option - do the delete by SQL, catch the error. If it > doesn't error, discard the object from the cache. -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer Try out the new Transfer ORM Custom Google Search: http://www.google.com/cse/home?cx=002375903941309441958:2s7wbd5ocb8 You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
