Tim Seaward

Well you have SO people commenting right here. The point I thought is to push the boundaries of performance and not support the widest number of use cases. As David...

I don't understand the point of this repo if you just want to improve the sql client under ado.net? You might as well work on fixing that under the hood....

This is my 2c as well. But I see it as an opportunity to write a new fresh DB surface area that while focused on Sql Server initially there is...

Just as a note, I don't really care, I just don't want to spend a PR redoing it all, so if you have a different preferred structure I am okay...

I recently hit this issue and found this and the protobuf-net info after a lot of searching, reverting to just pushing in a handler instead of a whole http client...

The skiplist always is all memory. If we come up with a strategy for moving the values off to a value log then the skiplist will be able to be...

I think key compression is a very good idea, especially on the disk files. I am not sure about the skiplist but that is why I would like to abstract...

Sorry i took so long on this . No currently however i am reviving this now and will work on the client.

Create the structure for holding and potentially compressing paths in memory as they are generated. Have the possibility to persist or dispose of the paths as calculations take place.

One added for loading from Json more needed for Xml, and other providers