UpdateRecord drops existing edges?

[josebalius]

So I was able to get UpdateRecord working but I started to run into a bug that took me a while to find.

Essentially I would create a record, attach some edges to it, and later on at some point I am using UpdateRecord to update it with some of the fields, but then I started to notice that all edges attached to that record were disappearing, and the queries that were expecting those edges to exist started to fail.

I can work on putting a test case together but have you run into this?

[dennwc]

UpdateRecord is a low level function. It will just replace the whole record with you data. It also means, that if you'll try to update record using struct without a certain field, it will just disappear. In fact, Orient stores all the links to edges in a specific field. I believe, that you have wiped it with an update)
You must first load an original Document, load struct into it, and then update the record.

[dennwc]

We definitely need an example for this case. It is not obvious at all. Linking to #31.

[josebalius]

@dennwc I'll work on a concrete example for this, but we need to document for sure that if you are not adding fields to your struct to map whatever edges your record might have, they will be lost when using UpdateRecord