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. vic On 12/14/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > > I know the company line on the SOC Schema Evolution code is that it will > be integrated into the trunk after enough people have tested it, but I > think this creates a chicken and egg problem. People aren't going to use > it until it's in trunk and it won't be in trunk until enough people test > it. > > Does it impact normal use without using schema evolution? In other > words, could it be integrated into trunk with the proviso that > > "The Schema Evolution feature should be considered beta. If you use this > feature, please test the results carefully and report any bugs you find. > If you don't use Schema Evolution, you shouldn't be affected." > > I'd really like to try it, but I don't have time to keep up to date with > two branches. > > Todd > > On Thu, 2006-12-14 at 21:22 +0800, Russell Keith-Magee wrote: > > On 12/13/06, Steve Hutton <[EMAIL PROTECTED]> wrote: > > > > > Does it have a realistic chance of being accepted into core if it's found > > > to be bug free? Is it fully documented? Is the design controversial or > > > does it follow a community consensus? > > > > There was discussion about the general problem of schema evolution > > before the SOC project was started. The discussion was started by > > Jacob, and other committers (Luke and Malcolm) weighed in at the time, > > along with many other interested onlookers. The resulting design is on > > the wiki. > > > > Assuming that the implementation matches the proposal, I would say > > there is a realistic chance of it getting accepted into core. However, > > this would require that the implementation is up to date, and bug free > > (including tests to validate this status that are integrated into the > > Django system tests). > > > > Yours, > > Russ Magee %-) > > > > > > > > > > -- "Never attribute to malice that which can be adequately explained by stupidity." - Hanlon's Razor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
