On 7/17/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > Not only for MySQL would this be handy, for other backends as well. I think > for PostgreSQL the inheritance feature would need this too.
How so? Postgres doesn't have multiple storage engines like MySQL does; a Postgres table is a Postgres table. SQLite doesn't have them either. Which is probably a very strong argument against it being a general model option. > What you guys and girls think? I think that if you need a specific storage engine for MySQL, you should have Django output the table creation statements into a file, edit them to add the storage engine info, then execute them ;) -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
