This allows for a Condition to be evaluated based
on two supplied values.

Signed-off-by: Dave Tucker <[email protected]>

The unmarshal methods didn't use pointer receivers

Go case statements don't fallthrough

While scalar values are easily type asserted when marshalled to an
interface{} the same is not true for map, set and uuid types.
We need to use reflect to determine the OVSDB type before storing
as an interface{} value.

Signed-off-by: Dave Tucker <[email protected]>

This was incorrectly disallowing mutations where a
single string would be inserted in to a []string...
or int, real etc...

Signed-off-by: Dave Tucker <[email protected]>

Signed-off-by: Dave Tucker <[email protected]>

Signed-off-by: Dave Tucker <[email protected]>

And rename Set to Create. This allows for a caller to
Add/Update/Delete cached rows with the appropriate locking.

Signed-off-by: Dave Tucker <[email protected]>

To make this work, we add NamedUUID detection.
A named UUID is considered a default value as it's yet to
have been processed by the server.

Signed-off-by: Dave Tucker <[email protected]>

This adds an initial in-memory server implementation.
It implements enough of the spec to be used for testing.

Signed-off-by: Dave Tucker <[email protected]>

This commit make a few changes to the cache.

1. Deprecates the TableCache.Set API, instead only allowing data to be
provided in a call to NewTableCache
2. Disallow RowCache creation via API and instead init the cache based on
the contents of the provided schema. This removes having calling code
check for table existence
3. Rename Row.Set to Row.Create and provide an additionally check the
type of the provided Model matches the schema
4. Cache row indexes for increased lookup speed

Signed-off-by: Dave Tucker <[email protected]>

Since the TableCache already does this, we don't need to implement
checks. Just check for errors on cache operations

Signed-off-by: Dave Tucker <[email protected]>

Signed-off-by: Dave Tucker <[email protected]>

1. Rename ninserts to inserts
2. Adds support for multiple clients in series/parallel
3. Ensures that we wait for the event to be received in cache

Signed-off-by: Dave Tucker <[email protected]>

This ensures minimal delay between sending a transact response and the
update notification being sent via monitor

Signed-off-by: Dave Tucker <[email protected]>

This removes the lock on TableCache and instead achieves the same
result by locking all of the RowCaches. This is possible because
the map in the TableCache doesn't change after creation, only the
contents of the RowCache.

Signed-off-by: Dave Tucker <[email protected]>

Signed-off-by: Dave Tucker <[email protected]>

Signed-off-by: Dave Tucker <[email protected]>