> I should be in a position to publish a git repository with my work in > progress in the next day or so, which will remove the need for anyone > to apply the patch manually. When I push the repository, I'll announce > on the ticket and on django-developers. Watch this space.
That'd be great, thanks a lot. > > > I tried unsuccesfully with django 1.0rc, 1.0 and 1.0.2, everytime > different > > rejections, and when I try to fix them by hand I always get a 'SELECT > FROM > > ...' invalid clause error. > > This error isn't one I can recall seeing during my work, so I'd need > to see more detail to help out here. The only error I am aware of with > the patch as published is that one of the test cases causes problems > with MySQL due to a quoting problem with a column name with a space in > it. This arises as a ProgrammingError during the test suite, not an > invalid clause error. > I also contacted Nicolas off list and he said he was gonna try to update the patch to work against trunk in the next days or so. So I think I would better wait a week or so and see what happens, I already read all the docs on the patch, this certainly looks great. Ariel. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
