v0.0.8

Changes 535cda2

fix: [getFirst] condition was using wrong indexes

The issue was due to a miss-configured test.
The expected value from 2 different
scenarios was the same.

That lead assert to pass both scenarios
while it should have failed on the second

Now tests have been updated and the wrong
condition that was returning a wrong value
fixed

v0.0.7

Commit: b8feaad

Before we were wrapping errors by adding
manually the callers name

Now we wrap errors by getting automatically
the callers name and line of code

v0.0.6

Commits:

• 5ddb5bf

In this commit we moved to a storage.Write
safer approach by including an intermediate
write to a different file to ensure that the
db will not get corrupted on non-graceful
program exits

Co-Author: reddit:user:jakewins

v0.0.5

Changes 664c4da

In this commit we fixed the GetFirst Method which
was exporting a different value when a branch with
the queried key in lower hierarchy was processed
first

In addition to that change, we made the following
changes:

• Updated Upsert wrapper to use directly upsertRecursive
• Exported Cache content
• SQL Now is a Pointer to Storage struct
• Minor changes e.g. remove redundant error function

v0.0.4

Improvements: 04343d6

• Simplified some functions logic
• Updated errors to provide a bit more info

v0.0.3

Improvements 44816b9

Tests

• Remove test-dbs at the end
• Include additional test cases

TestUpsert

• Add arrays
• Add arrays of maps
• Add map with arrays
• Add map with integers

TestGetSingle

• Get key with map values

TestGetPath

• Test array out of range errors

TestDelete

• Test delete missing key errors
• Add arrays of maps
• Add map with arrays
• Add map with integers

TestGetSingle

• Get key with map values

TestGetPath

• Test array out of range errors

TestDelete

• Test delete missing key errors

TestGet

• Include additional match that
  has a map as value rather than
  a string

cache

Export SQL.Cache
Before we had Cache struct exported
but SQL.cache unreported.
Now we have both objects exported

Error Wrap errors

We included error.wrap
during checks. Now among with the initial
error message it is also propagated the
caller name.

v0.0.2

Fixed findPath issues with arrays and updated documentation

v0.0.1

Initial release of yaml db