On Tuesday, 30 July, 2019 14:39, test user <example.com.use...@gmail.com> wrote:
>What I would like is something like BEGIN READ, which will not block >writers for its duration. I would think that adding a new lock type may be confusing and would prefer something like adding a SHARED or READ keyword after IMMEDIATE BEGIN IMMEDIATE [SHARED|[UPDATE]] [TRANSACTION] where the default is UPDATE if not specified. This will have the least effect on backwards compatibility but still makes it obvious that you are requesting an immediate lock, just a SHARED/READ lock rather than an intent to update lock. This syntax is closer to the SELECT ... FOR UPDATE OF ... used in some other SQL dialects to obtain specific intent locks at prepare time rather than depending on the ability to escalate the shared lock to intent on the retrieved table[/row] ... -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
