Re: [w3c/IndexedDB] Backward-compatible schema changes are very hard (#282) from Joshua Bell on 2019-09-20 (public-webapps-github@w3.org from September 2019)

From: Joshua Bell <notifications@github.com>
Date: Thu, 19 Sep 2019 18:25:53 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/282/533366398@github.com>

**TPAC 2019 Web Apps Indexed DB triage notes:**

Hey Jonas!

Potentially scary/complex change to implementations and adds API confusion, but the use case is clear. FYI we're looking at https://github.com/w3c/IndexedDB/issues/288#issuecomment-533359849 which doesn't address the big use case here (avoiding reloading everywhere), but does solve the minor version problem. We think using [Web Locks](https://wicg.github.io/web-locks/) could make the BroadcastChannel-style workaround easier. 

Leaving this open to gather more thoughts.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/282#issuecomment-533366398

Received on Friday, 20 September 2019 01:26:15 UTC