expo/troggle
2
0
Fork 1
mirror of https://expo.survex.com/repositories/troggle/.git synced 2026-01-18 22:22:53 +00:00
Code Issues 18 Projects 3 Activity

Can't edit same cave at the same time #17

New Issue
Open
opened 2023-08-04 21:59:14 +01:00 by xle · 3 comments
xle commented 2023-08-04 21:59:14 +01:00
Owner
Copy Link

In order to prevent merge errors and conflicts, people need to manually ascertain if someone else is editing a file: see Becka yelling "Is anyone editing 290?" in the tatty hut. It is 2023. SMA is a solved problem. Why is this necessary?

In order to prevent merge errors and conflicts, people need to manually ascertain if someone else is editing a file: see Becka yelling "Is anyone editing 290?" in the tatty hut. It is 2023. SMA is a solved problem. Why is this necessary?
xle added the Bug label 2023-08-04 21:59:14 +01:00
PhilipSargent commented 2023-08-04 22:39:00 +01:00
Member
Copy Link

because we have no file locking yet.
No work would actually be lost, because the data is commited to git as it is saved, but recovering it would be a pain.

because we have no file locking yet. No work would actually be lost, because the data is commited to git as it is saved, but recovering it would be a pain.
PhilipSargent commented 2023-08-05 12:27:37 +01:00
Member
Copy Link

From my to-do list:

Use select_for_update() and a transaction to prevent conflicts when 2 people try to save the same file. But MariaDB support lacking.

So yes, Django has the tools we need, but no, MariaDB doesn't support them. We would need to move to Postgres ?

From my to-do list: > Use select_for_update() and a transaction to prevent conflicts when 2 people try to save the same file. But MariaDB support lacking. So yes, Django has the tools we need, but no, MariaDB doesn't support them. We would need to move to Postgres ?
xle commented 2023-08-11 11:39:21 +01:00
Author
Owner
Copy Link

Migrating from MySQL to Postgres is not a difficult process: seems to be a very high ROI change in this case.

Migrating from MySQL to Postgres is not a difficult process: seems to be a very high ROI change in this case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Bug
Bug - something that doesn't work as it should do
 Enhancement
New feature or enhancement
 High Priority
Critical issue. Fix/implement ASAP
 Low Priority
Non-critical issue, nice-to-haves etc.
 Major Change
Change of large scope
 Minor Change
Change of small scope
No Label Bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
chi PhilipSargent xle
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: expo/troggle#17
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?