Future alignment with RDB specification?

[js-choi]

As @arthurhsu said in 2016-02, Lovefield functionally acts as a polyfill of the proposal for the web RDB specification—or, at least, “90% of it”. There are several differences between the APIs of Lovefield and RDB’s current draft, as documented in “rdb: Design Decisions” and “rdb-polyfill: README”. Some of these changes, of course, were made because many IndexedDB performance constraints may be ameliorated by natively provided SQL-type query engines.

However, other changes seem to be due to non-performance issues such as developer ergonomics. For example, “the new syntax [for defining tables, indices and constraints] is less verbose and easier to call,” and “observers are greatly simplified because the original observer design in Lovefield provides detailed information than needed in most cases.”

Are there plans to align Lovefield’s API further with RDB’s in a new major version, once RDB has been further standardized, to the extent that would still be performant with an IndexedDB implementation?

[arthurhsu]

Currently there is no plan to align the API since I did not secure support from within Chrome for RDB spec. Also Lovefield API changes are very unlikely since we have a very large deployment base and the cost of changing that does not justify in foreseeable future.