John Atten

Hi All - Thanks for your feedback and patience on this. I am unfortunately on the road at the moment, but I will try to see what's up with this...

@pascualito2000 Try now. @Lucas-S PR should fix this. Not sure where those odd paths came from, possibly my Mono implementation?

All of the above is why I held off on that for now. I don;t disagree, but I want to spend some time firming up the core functionality and API...

All of that said, it wouldn;t be difficult to create an `InMemoryList` from which the actual `BiggyList` could be derived. After all, all `BiggyList` does is keep an internal list...

I've been thinking about that. Not so much about more features, as: 1. Sweet, easy-to-use API 2. Solidify existing featureset, test extensively 3. Stable API, so we can get up...

No, but maybe make sure the existing comments are left in or updated to explain why it's needed. Does it do exactly the same thing as the code already in...

Yeah, the in-memory list won't be aware of changes made from another source to the Db. Might be interesting to see if there is a way to notify the Biggy...

I think the original thinking here is that in order to behave predictably across platforms, Biggy wants you to explicitly specify a PK. Meaning (in the case of SQLite), either...

Yeah, I dug pretty ddep into the SQLite docs on this (for a different thing). I'm pretty sure there's a sensible way to leverage the ROWID column the way you...

Hey Michael - Sorry, just got back from a business trip, catching up on email. I'll try to checko this out by the weekend. Any progress since this email? I...