In Mr Smiths examples, one statement effect is a direct result of an action
you (subjectively speaking) knowingly did, or did not do, to the car. You
did not fuel the car. You did take the wheels off. There by, your car is
essentially a hunk of metal taking up space. It doesn't function as
desi
On 2016/06/28 5:46 PM, John Found wrote:
On Wed, 29 Jun 2016 01:03:28 +1000
"dandl" wrote:
But if everything is configured right and working right and nothing bad
happens then it is highly reliable over very large volumes of transactions.
For me, this is a clear definition of the term "not
On Wed, 29 Jun 2016 01:03:28 +1000
"dandl" wrote:
> But if everything is configured right and working right and nothing bad
> happens then it is highly reliable over very large volumes of transactions.
For me, this is a clear definition of the term "not reliable". Isn't it?
--
http://fresh.fla
ginal Message-
> From: sqlite-users-boun...@mailinglists.sqlite.org [mailto:sqlite-users-
> boun...@mailinglists.sqlite.org] On Behalf Of Simon Slavin
> Sent: Tuesday, 28 June 2016 7:28 PM
> To: SQLite mailing list
> Subject: Re: [sqlite] Locking semantics are broken?
>
>
On Tue, 28 Jun 2016 at 19:17 Rowan Worth wrote:
> On 28 June 2016 at 16:07, dandl wrote:
>
> > > Do not use SQLite for concurrent access over a network connection.
> > Locking
> > > semantics are broken for most network filesystems, so you will have
> > > corruption issues that are no fault of S
On 28 Jun 2016, at 9:07am, dandl wrote:
>> Do not use SQLite for concurrent access over a network connection. Locking
>> semantics are broken for most network filesystems, so you will have
>> corruption issues that are no fault of SQLite.
>
> I have seen this comment made more than once on this
On 28 June 2016 at 16:07, dandl wrote:
> > Do not use SQLite for concurrent access over a network connection.
> Locking
> > semantics are broken for most network filesystems, so you will have
> > corruption issues that are no fault of SQLite.
>
> I have seen this comment made more than once on th
dandl wrote:
>> Do not use SQLite for concurrent access over a network connection. Locking
>> semantics are broken for most network filesystems, so you will have
>> corruption issues that are no fault of SQLite.
>
> I have seen this comment made more than once on this list. Is there any
> reliable
> Do not use SQLite for concurrent access over a network connection. Locking
> semantics are broken for most network filesystems, so you will have
> corruption issues that are no fault of SQLite.
I have seen this comment made more than once on this list. Is there any
reliable evidence to support
9 matches
Mail list logo
