Mauricio David

Yes, I have plans to LiteDB v5 migrate from earlier versions... but will be a migration. After open datafile in LiteDB Studio, you datafile will be converted into new format.

Hi @gmgunderground, there is no create table. You can insert data into a new collection that will auto create this collection. Use: ```SQL INSERT INTO mycoll VALUES {_id:1, name: 'John'};...

Hi @HolyOne, when you first open your datafile in LiteDB Studio, this file are upgraded into new file format (used in LiteDB v5). After this, you can't back to v4...

Hi @tiksn, I will read more about Chocolatey package to discover how publish there. Thanks!

Hi @digitalcoyote, thanks for this. I will release new version tomorrow (0.6) and version 1.0 in Jan/31.

Yes, wait a bit more will be great. Next version will support full search, expressions and includes (DbRef), like `db.mycol.find _id > 0 and LOWER(name) startsWith 'john' include "$.customers[*]"` Also,...

And after this error occurs, if you open in LiteDB.Studio and run a simple `SELECT $ FROM collection` you see if you lost any data?

Humm... much better. Maybe was a clean buffer page in a wrong moment. I will review this and add more error detail message so, if occurs again, will be better...

Sorry, I didn't understand this: "Is this code-path unique to upsert?" v5.0.2 is compatible with v5.0.1...

It's not about `Upsert`. Upsert is only a Update + Insert command. This occurs in adding a new index node (possible for `_id`). Engine try load a page from disk...