davebshow
commented
8 years ago I understand that one of the benefits of using a graph database is their flexibility. For example, in the case of Titan:db, you are encouraged to define a schema for your data, but it isn't required. However, due to the fact that Goblin is an OGM designed to encourage consistent mapping between the application and database data models, we believe that it is best not to allow this type of property setting by default. Furthermore, Goblin is designed to internally handle property names and does not map user defined property names exactly to the database.
If you want to do this, you can still use goblin, but you will have to handle it by submitting a script manually using connection.execute_query or the gremlin.GremlinMethod class. To use the example code you gave me earlier:
from goblin import properties
from goblin import connection
from goblin.models import Vertex
from goblin.models.element import Element
from tornado import gen
from tornado.ioloop import IOLoop
class TestVertex(Vertex):
prop1 = properties.String()
@gen.coroutine
def manual_update(self, key, val, **kwargs):
script = 'v = g.V(vid).next(); v.property(k1, v1); v'
bindings = {'vid': self.id, 'k1': key, 'v1': val}
future = connection.get_future(kwargs)
resp = yield connection.execute_query(
script, bindings=bindings, **kwargs)
msg = yield resp.read()
return Element.deserialize(msg.data[0])
@gen.coroutine
def go():
v = yield TestVertex.create(prop1='A')
print(v)
modified_v = yield v.manual_update('prop2', 'B')
print(modified_v)
print("Manual values: {}".format(modified_v._manual_values))
if __name__ == '__main__':
connection.setup('ws://localhost:8182')
loop = IOLoop.current()
try:
print("start")
loop.run_sync(go)
print("end")
except Exception as err:
print("Caught an errror: {}".format(err))
raise err
finally:
connection.tear_down()
loop.close()
However, I would like to note that this is not ideal for most use cases; it is generally better to update the model definition to reflect the new property.
dusktreader
Instead of erroring out when trying to set a property that is not 'officially' part of the class, I enabled the property to be set using the same mechanism that is used in the constructor.
This allows additional properties outside of those described explicitly in the class to be saved via an update