-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark/neoid with json field support #28
base: master
Are you sure you want to change the base?
Mark/neoid with json field support #28
Conversation
Perhaps something like this could be extracted into, say, a neoid-postgresql module or similar? What are your thoughts? |
I agree. Not a lot people would be using json field in their db yet. Let me |
@glsignal : hi Greg, so If I want to override the to_neo function in |
I suppose that depends on whether the additions can cope with (or be adapted to) being run either before or after the original method, in which case you could just call I'm about to board a flight, but can probably look at it a little more and give you a better answer later on. Rewriting the original and adding additional code will prevent it from getting updates from neoid, should that method be updated in some future revision. Edit: forget the super approach; http://stackoverflow.com/questions/4470108/when-monkey-patching-a-method-can-you-call-the-overridden-method-from-the-new-i |
@exklamationmark Sorry my availability to help out on this has dropped to nil I'm afraid :( |
No worry. I think I get the idea. Thanks for your help, Greg Best regards, On Mon, Sep 16, 2013 at 7:08 PM, Greg Signal [email protected]:
|
No PRs are currently being merged until tests are passing again on Travis. Apologies, but I will review and implement after I have stabilized Neoid for version 0.2.0. |
PRs are now being accepted. @exklamationmark if you could rebase, I will look into getting this feature in. |
I was working on an application that runs dual db: PostgreSQL 9.2 and Neo4j, where a model have a json-type field. This wasn't able translatable using the original neoidable config.
So I wrote added a json_field definition that allows json-type fields to be used in Neoid. Basically this will add the content of the json_field to neo4j node.
A drawback is that I can't test this on sqlite3 in-memory db, so I have to create a local postgres db to test. I am open to suggestions on this, though