On Thu, 13 Oct 2011 11:22:20 +0200, bls wrote: > Am 12.10.2011 20:13, schrieb Steve Teale: >> The way this discussion is going we're going to have four layers, with >> the top one written by Jacob. > > 1 = etc.c. > 2 = Database classes > 3 = ?? > 4 = ORM > > Please explain ?
What I meant was that there might be a layer here that would provide a common interface to the supported databases in terms of literal SQL commands, as embodied in Andrei's example > >> I'm lost with this ORM stuff, and I suspect that the vast majority of D >> users would feel the same. > > > IMO, SQLAlchemy (Python) is a very clean and powerful ORM. Easy to use > and provides the _Data Mapper_ pattern (not everybody is enthusiastic > about the Active Record pattern) as well as the _Unit Of Work_ pattern. > > The UOW pattern organizes pending insert/update/delete operations into > queues and flushes them all in one batch. (All or nothing way, in other > words transactional. > > just in case : http://www.sqlalchemy.org/docs/orm/tutorial.html
