On 7/17/06, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > 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.
But pretty much all of those options are, again, specific to the particular database they go with. An ORM layer cannot and should not attempt to emulate every possible configuration of every possible RDBMS it can be used with; that way lies madness, What it should support is: 1) The features common to all the RDBMS products it can be used with. 2) A way to manually tweak its SQL output to take advantage of features which only apply to one database. > 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? :) I dunno. Most of the apps I write are for me or my employer to use ;) Do you have a proposal for dealing with the complex snarl of options we'd end up with if we went down this road? -- "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 -~----------~----~----~----~------~----~------~--~---
