Re:DuckDB – An embeddable SQL database like SQLite, but supp...
by viraptor on Saturday September 19, 2020 @11:22PM
(#24531682)
Those solutions still have a high overhead. There's acid compliance, serialisation in memory, maintaining indices, and many other layers. Compare it to an ideal testing solution with no initialisation cost and insert being literally: parse the query, add a new entry to a list, done.
[ Parent
| on HN ]
Re:DuckDB – An embeddable SQL database like SQLite, but supp...
by RantyDave on Saturday September 19, 2020 @11:39PM
(#24531725)
But you want to be testing against something that is as close as possible to the deployment environment. So if that means acid, indices etc, then that's what it is.
Re:DuckDB – An embeddable SQL database like SQLite, but supp...
by viraptor on Sunday September 20, 2020 @12:01AM
(#24531796)
You can still do them in a trivial way that works like production. For example: if some column has a unique index, look at all rows and compare the new value. You don't need an actual index for it. (And definitely not a fancy concurrent access btree) For transactions/mvcc you can literally make a copy of everything.