Currently the transaction is by default a writable transaction.
It should default to a readonly transaction and the command line should have a switch to make it writable.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
I found the name of the flag "writable" very astonishing and not related to SQL naming.
At the end I think we should keep by default a normal transaction and have an option to start a readonly transaction as SQL does. Because it is only if the user is calling commit that it will alter the data.
Also it is better to keep a backward compatible behavior.
>I found the name of the flag "writable" very astonishing and not related to SQL naming.
I searched for an antonym of readonly. It's the best I came up for.
>At the end I think we should keep by default a normal transaction and have an
>option to start a readonly transaction as SQL does. Because it is only if the
>user is calling commit that it will alter the data.
>
>Also it is better to keep a backward compatible behavior.
OK I'll use readonly if we're going for the reverse.