3 ms·
Actually, in my code I always start with low(): low('foo').insert({ name: 'foo' }) low('bar').insert({ name: 'bar' }) low('foo').insert({ name: 'foo' })
by typicode 12y ago
Actually, in my code I always start with low():
low('foo').insert({ name: 'foo' })
low('bar').insert({ name: 'bar' })
low('foo').insert({ name: 'foo' })
So never really considered this way of writing or had this bug.
But I can see that it's a flaw and unexpected behavior. I'm adding this to the enhancements for the next version.
Thanks for spotting it :)
- typicode 12y agoJust a little update. I've released LowDB 0.4.0 which is a complete rewrite of the project. It fixes some initial flaws/bugs and includes some new features. Also, writing is now fault-tolerant and fully asynchronous.