On Fri, Dec 4, 2009 at 6:31 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote:
[snip] > 1) Do nothing special. This is the currently implement behaviour. As the default, this seems to be the intended behavior only in rare cases (overwriting a different object from the original) and will indeed bite. There is another option: leave in the hands of the user (as you say) but make them explicitly say which behavior they want of the following: > 2) Set the primary key of the object to None so that the save on the > new database is guaranteed to be an insertion, rather than a possible > overwrite of an object with the same pk value on the second database. > > 3) Transform the save into a 'force insert' if the database changes. > This will raise errors if the pk is already in use on > > 4) Use the PK on the old database and issue a deletion before saving > to the new database. If they didn't explicitly indicate which of these to do, then raise an error. Just a thought. -Doug [snip] > I'm open to any other suggestions - and for any offers to help out :-) > > Russ %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
