Ensure atomic database operations #315

New Issue

Jef Roosens · 2022-12-17T12:47:47+01:00

Jef Roosens commented

2022-12-17 12:47:47 +01:00

The database layer currently doesn't really bother with checking whether it's receiving requests concurrently. However, with the addition of a server-agent architecture, the server could start receiving a lot more requests, making a collision more likely.

This should be as easy as making the vieterDb.conn field shared and locking it for operations.

The database layer currently doesn't really bother with checking whether it's receiving requests concurrently. However, with the addition of a server-agent architecture, the server could start receiving a lot more requests, making a collision more likely. This *should* be as easy as making the `vieterDb.conn` field shared and locking it for operations.

Jef Roosens added the

enhancement

label 2022-12-17 12:47:47 +01:00

Jef Roosens added this to the 0.5.0 milestone 2022-12-22 13:09:48 +01:00

Jef Roosens commented

2022-12-22 20:49:30 +01:00

Poster

According to the SQLite docs, this already happens by default if not specified.

According to the [SQLite docs](https://www.sqlite.org/threadsafe.html), this already happens by default if not specified.

Jef Roosens closed this issue

2022-12-22 20:49:30 +01:00

Sign in to join this conversation.