[postmodern-devel] Exlcuding slots dao-save

[Phil Marneweck]

I have test cases but I need to clean them up and I want to just have
one last look (most of it as done late last night and code looks
different in the morening ;)) before I mail it to you. 

One issue I have is that if you make a new instance of a dao and the
record alread exist in the db and you run save on this the record the
update is done correctly. It does not however populate the oid in an
update only in an insert. I am not sure whether this is postmodern's
problem or the users.

For me it is in a sense the user/programmer problem. However letting
postmodern protect itself against such would keep the is this a bug or
feature mails on the mailing list down to a minumum.

The only other time that I can think of that this could become an issue
is if the user has triggers on the table that change data before it goes
into the db. Then updating the object after a an update would be
essential but then you cant just check for unbound slots you have to
check all the fields.



On Mon, 2009-10-26 at 07:44 +0100, Marijn Haverbeke wrote:
> > Took a life time longer but it looks like i got it working without
> > mangling the code to badly.
> 
> Great! I'd be happy to review it and merge it into my repo. If you
> have a test case that demonstrates how you're using this, that would
> also help.
> 
> _______________________________________________
> postmodern-devel mailing list
> postmodern-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel