On Wed, 23 Nov 2005 07:30:54 -0500 James Bennett wrote: > Now, probably the overwhelming majority > of new developers adopting Django are not going to be integrating with > legacy databases, and in any case they wouldn't do it by pointing at > their production DB. So one way or another, the first step is *always* > going to be specifying the model. What usability gain, then, is there > in making this specification vary depending on the inconsistencies and > idiosyncracies of different database systems, when right now we have a > perfectly good way of specifying models which has one and only one > syntax that a developer must learn?
This single syntax also enables ace stuff like testing using an in-memory throwaway SQLite database (can't find the link right now), or developing in environments where all you have is SQLite, or some database that isn't your production DB. Luke -- Parenthetical remarks (however relevant) are unnecessary Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/
