Hi James, James Bennett wrote: > 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.
This storage engine choice was only an example. There are lots of other options which can be set per table. As Honza replied, this is not MySQL specific and PostgreSQL as well as other DBMS accept options like these. >> 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 ;) Wrong. You make a application mostly because you would like to distribute them. You make it easy for people to install it and use it. Why else we make frameworks? To tell users to use awk and sed? :) It's a minimal addition which will solve lots of requests. Cheers, Geert -- Geert Vanderkelen, Support Engineer MySQL GmbH, Germany, www.mysql.com Hauptsitz: MySQL GmbH, Radlkoferstr. 2, D-81373 München Geschäftsführer: Hans von Bell, Kaj Arnö - HRB München 162140 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
