That's a good point. Thank you Keith!
On Thu, Feb 2, 2017 at 12:12 AM, Keith Medcalf wrote:
> If it is a remote filesystem (vs a local filesystem) then you must also
> have only one connection (ever) to the database file at any given time.
> Otherwise you may have issues. (Note "Single User" do
If it is a remote filesystem (vs a local filesystem) then you must also have
only one connection (ever) to the database file at any given time. Otherwise
you may have issues. (Note "Single User" does not mean "Single Connection")
> Hi Simon. Thank you for your answer. It's single user and wit
s-boun...@mailinglists.sqlite.org]
> On Behalf Of Sebastián Guevara
> Sent: Wednesday, 1 February, 2017 12:09
> To: sqlite-users@mailinglists.sqlite.org
> Subject: [sqlite] Sqlite with Docker and mounted volumes
>
> Hello to all. We are contemplating using SQLite from within a Docker
> co
Hi Simon. Thank you for your answer. It's single user and without
concurrency.
On Feb 1, 2017 18:32, "Simon Slavin" wrote:
On 1 Feb 2017, at 5:08pm, Sebastián Guevara
wrote:
> Hello to all. We are contemplating using SQLite from within a Docker
> container accessing a DB on a mounted volume
On 1 Feb 2017, at 5:08pm, Sebastián Guevara wrote:
> Hello to all. We are contemplating using SQLite from within a Docker
> container accessing a DB on a mounted volume.
Does your setup involve two or more users accessing the data at the same time ?
It’s possible that locking won't work prope
Hello to all. We are contemplating using SQLite from within a Docker
container accessing a DB on a mounted volume. I don't expect any
performance issues if the mounted volume is a directory from the host
machine. But what if it's a shared storage, something like Flocker (
https://clusterhq.com/flo
6 matches
Mail list logo
