On 9/12/07, David Binger  wrote:
> Mike, I wish your Durus example had Flintstone as a subclass of
> Persistent.
> In application-level Durus code calls to _p_note_change() should be
> rare,
> and this is especially true in code that is intended as an introduction.
> (I do, however, understand that you wrote it that way to be storage-
> neutral.)

I did originally have it as a subclass of Persistent.  Then I had a
bug in a query and tried to load it in the durus command-line client,
but I couldn't because it couldn't find the Flintstone class (couldn't
find '__main__.Flintstone').  So I moved to a seperate module, and
that's when I made it non-persistent so both classes could share it.


BTW, I put in ._p_note_change only because it bit me. After .abort()
the database was correct but the memory objects weren't rolled back.

When I get to work I'll see about making it Persistent again.

--
Mike Orr