-
Notifications
You must be signed in to change notification settings - Fork 15
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
unable to handle tables without primary key #10
Comments
This is a good point. I have some discussion in this realm here: #8 but it should definitely be addressed more thoroughly. I've put this on my list (though you're welcome to look into it as well) |
I'd love to help but my knowledge of ruby is limited to Chef recipes... |
I totally understand and no worries. If you would like to help I'll give you (and anyone else reading) a quick rundown of how the gem works below. You're also welcome to drop by our chat room on Gitter So the quick overview: The gem depends on neo4apis which is a gem that lets you set up a class which you can then hand objects to and which will take those objects and create Neo4j nodes and relationships from them. The main file that does that for https://github.com/neo4jrb/neo4apis-activerecord/blob/master/lib/neo4apis/activerecord.rb In the end what that's doing is calling the Lastly there is a CLI (command-line interface) class which inherits from So again, I wrote that because it's good to have out there. This gem might be a lot if you're not as familiar with Ruby or ActiveRecord, but you've got to start somewhere, right? ;) Important note: Something that I just thought of. I'm not sure how you're using the gem, but if you're defining some |
Hi, that is the blog post I read before trying out the tools... I'm currently trying to generate the CQL using SQL... let's see how that |
/Library/Ruby/Gems/2.0.0/gems/neo4apis-activerecord-0.8.0/lib/neo4apis/table_resolver.rb:29:in `block in identify_primary_key': Could not find a primary key for AccountContentset. (Neo4Apis::TableResolver::UnfoundPrimaryKeyError)
The table in question contains 2 foreign keys and is just used to form a many to many relationship.
The text was updated successfully, but these errors were encountered: