vieter-v/vieter

Archived

Ensure atomic database operations #315

New issue

Closed

opened 2022-12-17 12:47:47 +01:00 by Jef Roosens · 1 comment

Jef Roosens commented

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

Owner

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

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

Author

Owner

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

This repository is archived. You cannot comment on issues.

No labels

good first issue

No milestone

No project

No assignees

1 participant

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#315

No description provided.