You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
indexeddb is meant to be SQLite replacement for web, it's literally a built-in SQLite, with the same types, etc. And I'm interested if this use-case was considered with tuql.
If you'd ask: "why the hell you need GraphQL layer for indexeddb", - I'd answer that it opens interesting capabilities of switching between local/remote queries, while just syncing the storage in background.
The text was updated successfully, but these errors were encountered:
indexeddb is meant to be SQLite replacement for web, it's literally a built-in SQLite, with the same types, etc. And I'm interested if this use-case was considered with tuql.
The text was updated successfully, but these errors were encountered: