On Mar 2, 2007, at 12:50, mario__ wrote:
> > On Feb 27, 8:31 pm, "Marc Fargas Esteve" <[EMAIL PROTECTED]> wrote: >> -1 on option 1, and +1 in option 2. We should not remove >> functionality because MySQL can't deal with that, simply document >> "this won't work with mysql" :) >> > > +1 Great! Then I'll relaunch my proposal for 'Choose Storage Engine per Model' :) -1 , unless it can be fixed in code and not manual.. Because saying it 'Does not work with MySQL' is false. It depends. -- Geert Vanderkelen http://some-abstract-type.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
