[EMAIL PROTECTED] wrote: > "*manual* orm mapping" , I mean doing the sql manually. > I think a generalized ORM layer isn't really needed unless youre going > to do lots of throwaway databases, as you might need for some > user feedback handling public web site , which from interview movie > posted earlier, is what django was for , some mass media/ interactive > advertising > web site .
Perhaps, although personally I think that the future lies in "meta-applications", in which a great deal about how an application behaves and works is "soft-coded" or otherwise specified by non-programmers. In such meta-applications, use of a generalised ORM layer for everything, or for as much as possible, is highly desirable. > Wonder if these ORMs do database versioning well e.g. > you change your object definitions, and it generates ALTER TABLE > statements to match. Sure - see http://erosson.com/migrate/ for the SQLalchemy ORM used in Django and TurboGears. Tim C _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
