[Seaside] How do you handle constraints on persisted collections?
boris at deepcovelabs.com
Tue May 19 22:25:18 UTC 2009
Clearly this would complicate the problem even further proving my point
From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Ramon
Sent: Tuesday, May 19, 2009 3:22 PM
To: 'Seaside - general discussion'
Subject: RE: [Seaside] How do you handle constraints on persisted
> Although, if two users are updating their usernames in separate
> transactions (say, in GemStone), this would do nothing to prevent both
> of them from succeeding, thus, this type of constraint checking really
> only applies when adding users to a collection which would stop this
> from happening by virtue of a commit conflict, no?
Not if you're using a reduced conflict collection to allow concurrent
updates of the collection, but otherwise yea you'd get a commit
seaside mailing list
seaside at lists.squeakfoundation.org
More information about the seaside