21 Aug
2008
21 Aug
'08
11:20 p.m.
On Thu, August 21, 2008 1:24 pm, Lukas Renggli wrote:
If the DB handles commit conflicts for you, there is
no need for
Magritte to do these checks for you. I remember doing some special
memento class for OmniBase that used the mechanisms of the OODB to check
for conflicts and to mark the changed parts as dirty.
If you don't want to check for conflicts you can simply replace the
method
Object>>#mementoClass to return MACachedMemento.
I guess I'd like to have Magritte figure out if I need to issue a
'commit' or a roll-back and go from there..
I guess I'd like to know what the difference is between the following
(perhaps a good FAQ entry?):
1) MACachedMemento
2) MARealMemento
3) MACheckedMemento
4) MARealCheckedMemento
5) MAStraitMemento
Also -- is there a good place to read up on the object comparison operators
such as #=, #<, #>? I've got a single ST book (in pdf form -- Smalltalk
by example) and didn't find any references to #= when doing a search and
little talk on comparisons..
Thx!