Skip to content
This repository has been archived by the owner on Jan 18, 2025. It is now read-only.

Support non-string keys for LinkMaps #11

Open
quux00 opened this issue Jul 28, 2015 · 0 comments
Open

Support non-string keys for LinkMaps #11

quux00 opened this issue Jul 28, 2015 · 0 comments
Assignees

Comments

@quux00
Copy link
Contributor

quux00 commented Jul 28, 2015

Currently, the ogonori LinkMap implementation - for both reading (deserializing) and writing (serialization) only support string keys. The map is of the form:

map[string]*oschema.OLink

However, according to the OrientDB schemaless serialization docs (http://orientdb.com/docs/last/orientdb.wiki/Record-Schemaless-Binary-Serialization.html), the key for a LinkMap is allowed to be:

STRING,SHORT,INTEGER,LONG,BYTE,DATE,DECIMAL,DATETIME,DATA,FLOAT,DOUBLE

Modify ogonori to support this. This will primarily involve changing obinary/binserde.go - the readLinkMap and writeLinkMap methods, and then updating the client.go functional test. Other parts may need to change as well.

quux00 added a commit that referenced this issue Jul 28, 2015
Currently only string keys are supported. Issue #11
was created to support non-string keys for LinkMaps.
@quux00 quux00 changed the title Support non-string keys for LinkMaps Story: Support non-string keys for LinkMaps Jul 29, 2015
@dennwc dennwc changed the title Story: Support non-string keys for LinkMaps Support non-string keys for LinkMaps Sep 16, 2015
@dennwc dennwc self-assigned this Sep 16, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants