On 2006-12-14, Victor Ng <[EMAIL PROTECTED]> wrote: > > The patch I previous sent in mostly adds a couple functions to the > psycopg2 backend in the introspection module. The only big changes > that affect the mainline django code are in django.core.management. > > I'm using my patches, so that's been tested through 3 schema updates > in production. As previously mentioned -there are those 2 remaining > bugs in the schema-evo code, but they're not show stoppers for me. > > I see no reason why people need to use the latest trunk to test beta > quality features. That just makes no sense - if you need beta > features - use a branch, or apply my patch to your own copy of trunk. > Is there a problem that I'm not seeing? I'm quite sure that all the > code that my patch modifies hasn't been touched in over a month, so it > should apply cleanly to trunk.
Victor, thanks very much for your efforts on this. I will be starting a new project soon and would like to test schema evolution. Can you explain the differences between your patch and the schema evolution branch itself? Are you proposing that your changes be rolled be rolled into the schema evolution branch? Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
