Content
@
0 reply
0 recast
0 reaction
Kevin
@typedarray.eth
Should Ponder replace SQLite with PGlite (pglite.dev) as the dev database? Pros: 1) Less magic/astonishment ("wait, what database am I using rn?") 2) Simpler schema definition API (currently stuck with the subset of stuff that both PG and SQLite support)
10 replies
3 recasts
142 reactions
Kevin
@typedarray.eth
3) No change to the local dev experience (one Node.js process, don't have to run a PG server) Cons: 1) PGlite is immature 2) Locking into PG could be a bad idea - is it better to stick with the narrow subset approach, and add support for even more databases? (doubt)
0 reply
0 recast
13 reactions
