This repository has been archived by the owner on Jun 11, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Goblin constructs property keys with hypercorrective zeal #31
Comments
I think the following is related: import asyncio
from goblin import connection
from gremlinclient import aiohttp_client
from graph_service.models import fiber
@asyncio.coroutine
def main_coro():
structure = yield from fiber.Structure.get('8036408')
print(structure)
structure.hatch_height += 1
resp = yield from structure.save()
print(resp)
def main():
loop = asyncio.get_event_loop()
connection.setup("ws://localhost:8182", pool_class=aiohttp_client.Pool, future_class=asyncio.Future)
loop.run_until_complete(main_coro())
if __name__ == "__main__":
main() This results in:
Note that the vertex label is prepended to the property key by goblin even though the property key was already in the form vertexlabel_propertyname. This is a titan instance with the automatic schema generation turned off. The property keys were defined in titan to conform to goblin's convention. |
leifurhauks
changed the title
Mapping between property keys and Goblin properties
Goblin constructs property keys with hypercorrective zeal
Jun 30, 2016
I'm back and just about ready to get to work. I believe this is happening due to the fact you are using |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the following model definition:
I have a 'foo' vertex in the database already with 'bar' = 'testing123'.
The following retrieves it and correctly prints 'testing123':
If I now change foo.bar and save it:
The
foo_property
coroutine now prints 'different value' as expected. But now the 'bar' property appears to be mapped to a new property, 'foo_bar' in titan:The text was updated successfully, but these errors were encountered: