[PEAK] peak.model & peak.storage viability?

[Ulrich Eck]

Am Montag, den 02.05.2005, 12:20 -0700 schrieb John Landahl:
> On Fri, Apr 29, 2005 at 01:15:03PM -0400, Erik Rose wrote:
> > ...
> > I'd likely base my solution on Ulrich Eck's sqldm package (posted here 
> > on 10/10/2003), which provides SQL-specific subclasses of EntityDM and 
> > QueryDM. They do reference _p_oid and _p_jar but not so much that I 
> > fear being unable to fix them when the underlying persistence machinery 
> > does change.
> 
> The code also uses the old binding API, so it's not going to work as-is.
> I'd also like to make use of this code, or something like it, for a
> large-ish project I'm about to start.  Ulrich, if you're listening, any
> objections to me putting an updated version of your code on PeakPlace?

go ahead, if what's in my cvs at:
http://cvs.net-labs.de/cgi-bin/viewcvs.cgi/libs/nll/src/nll/database/sqldm/datamanager.py
isn't working or not uptodate. i also have no objection against taking
it out of nll and package it with some docs or the like.

one thing that i allways wanted to change is: get rid of the meta-class
by using binding.Make (the only showstopper currently is the option, to
extend SQL-DM Classes by adding field-specs in subclasses, which i would
call YAGNI for now).


cheers ulrich

> 
> - John
> _______________________________________________
> PEAK mailing list
> PEAK at eby-sarna.com
> http://www.eby-sarna.com/mailman/listinfo/peak
-- 
Ulrich Eck <lists at net-labs.de>