#1373 magic-removal: MySQL does not support DROP CONSTRAINT
There was a diff submitted by Geert Vanderkelen awhile ago. It doesn't apply cleanly to 'core/management.py' anymore. Is there a reason it wasn't commited? If I fix it to work with current release will someone commit it? I assume svn ci is restricted. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: #1373 magic-removal: MySQL does not support DROP CONSTRAINT
Jacob Kaplan-Moss wrote: > On Apr 21, 2006, at 7:10 AM, njharman wrote: > >>There was a diff submitted by Geert Vanderkelen awhile ago. It >>doesn't >>apply cleanly to 'core/management.py' anymore. >>If I fix it to work with current release will someone commit it? I >>assume svn ci is restricted. > Yes, please do. new patch attached to ticket 1373 diffed against MR-r2717. Passes unittest. Works for mysql, assumed other backends work. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
ticket #347 mysql engine used for tables
Ticket marked wontfix. Seems rather harsh to force MySQL users into editing output of manage.py and commands like 'install' just won't work. Politely asking if this decision might be reconsidered if a clean solution could be found. If not, a warning / note in the docs about the limitations of MySQL and workarounds would likely save some people from grief. btw the transaction unittests fail with mysql backend because default MyISAM silently accepts but does not implement transactions. -- norm --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
models.py vs models/__init__.py
It's a bit hard trying to piece together the history of this from listarchives and tickets. It seems that putting models in a package instead of 'models.py' should work and is believed to work. I can verify that for MR-r2717 'models/__init__.py' does not work. In that 'manage.py sql' produces no sql for models. as outlined in this post to users http://groups.google.com/group/django-users/browse_thread/thread/454a9818f2786421/4e2cd192eb2588be#4e2cd192eb2588be There was some mention of __all__ so I tried adding that to my 'models/__init__.py' and listing my model classes but that didn't help. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: ticket #347 mysql engine used for tables
Michael Radziej wrote: > njharman wrote: >>Ticket marked wontfix. Seems rather harsh to force MySQL users into >>editing output of manage.py and commands like 'install' just won't work. > Alternatively, set default table type in your database to InnoDB, and > you're fine. Didn't know such a thing was possible, how excellent. Thanks. command line --default-table-type my.cnf default-table-type SQL SET table_type=INNODB; --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: ticket #347 mysql engine used for tables
DavidA wrote: > Maybe I don't understand the implications but I have been using > ENGINE=MyISAM on my tables so I can use MySQLs full-text indexing (not > supported by InnoDB). > > Does this thread imply that I can no longer use MyISAM tables with > MySQL? Or just that if I do, I must tweak the output of manage.py > (which I already need to do to add the engine and fulltext clases). No, much the opposite. MySQL uses MyISAM by default. You have to do something extra to get it to use another engine. MyISAM doesn't do transactions. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
