On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote: > > Russell Keith-Magee wrote: > > The latter, by comparing the signature of the models.py that you have > > with the signature in the Evolution table. The evolution table > > contains the signature of the last model that was sync'd; if this > > doesn't correspond to the current model, you need migrations to update > > the database. > > ok, i get that. i didn't realize you meant storing the entire model > structure in the db. (might want to avoid calling this a signature for > clarity, but that's semantics)
It's not the _model_ per se - just a rendition of the significant data in the model. > so now you have two models to diff. how do you detect renames? AFAICT, you _can't_ detect a rename with with 100% reliability. Whatever scheme you propose will be subject to either: - False positives: identifying deletion of X and addition of Y as an X->Y rename because the non-name attributes of X and Y are identical, or - False negatives (identifying rename X->Y as a delete of X and an add of Y because the attributes of X and Y aren't similar enough). Either outcome is undesirable for a real database. This is why the 'hint and tweak' approach is so essential. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
