Hello David,
I note that nothing has happened.
In future I would suggest that you simply tell people that document updates
are not really welcome. Otherwise you waste people's time.
The locking issue is actually quite serious.
Cheers,
Anthony
On Tue, Aug 3, 2021 at 10:01 AM Anthony Be
Hello David,
Thanks for that, I had thought that you were a committer. Sounds like it
might all be a bit too difficult.
Anthony
On Tue, Aug 3, 2021 at 9:39 AM David G. Johnston
wrote:
> On Mon, Aug 2, 2021 at 4:30 PM Anthony Berglas
> wrote:
>
>> You are talking about opt
tick? (i.e. does it run
the clock forward). I have another reason to know that. Using clocks is
iffy for synchronization.
On Tue, Aug 3, 2021 at 1:26 AM David G. Johnston
wrote:
> On Sun, Aug 1, 2021 at 11:35 PM Anthony Berglas
> wrote:
>
>> I have attached a proposed doc update
but changed should produce an error for Read Committed. The goal is not to
satisfy academic rules but produce something that works safely in
practice. But I am sure there has been much discussion about that
elsewhere.)
On Fri, Jul 30, 2021 at 6:03 PM Anthony Berglas wrote:
> OK, I
OK, I'll put something for you to review. Most programmers simply ignore
locking and wonder why it sometimes goes wrong.
On Fri, Jul 30, 2021 at 2:22 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thu, Jul 29, 2021 at 8:44 PM Anthony Berglas
> wrote:
>
>&
My point is that while I can follow the academic style discussion, most of
my colleagues could not. They just need to have a clear idea of how to
handle the common case, which is to use a database using some programming
language.
Early on, for Read Committed, it should discuss and ideally provide
