Murray @ PlanetThoughtful wrote:
Hi All,
I'm developing a wiki-esque application for an in-house project and am
wondering how others go about resolving potential conflicts when multiple
users are editing the same content drawn from a MySQL database?
You might want to ask in a mysql group about
]
Subject: Re: [PHP] Best practise for resolving potential conflicts when
editing db content?
Murray @ PlanetThoughtful wrote:
Hi All,
I'm developing a wiki-esque application for an in-house project and am
wondering how others go about resolving potential conflicts when multiple
users are editing
I'm not sure table locking is the answer. I'm not talking about
concurrency
in the sense of 'simultaneous' updates and selects, but in the sense
of an
'open record edit session' that predictably will overwrite the value
of a
record that may have been changed, after the edit session began, but
On Tue, 12 Oct 2004 02:41:10 +1000, Murray @ PlanetThoughtful
[EMAIL PROTECTED] wrote:
User A finishes his or her page edit and commits the changes, but the
underlying record was already changed by User B's page rename. User A's edit
changes overwrite this update in the record in question, and
Hi All,
I'm developing a wiki-esque application for an in-house project and am
wondering how others go about resolving potential conflicts when multiple
users are editing the same content drawn from a MySQL database?
In particular, I'm working on code that allows users to rename 'pages'
5 matches
Mail list logo
