Even a seasoned developer is still a newbie when s/he is exploring something new. I've been a professional developer for 18 years, and all this is new to me. I'm writing the tutorial that I would have liked to have found, in addition to ReadMes and online references written succinctly in Markdown.
Been trying to debug a problem I am having.
Added to Server:
Meteor.N4JDB.listen(function(query, opts){
console.log('Incoming query: ' + query, opts);
});
Which shows:
I20150921-01:17:13.550(0)? Incoming query: MATCH (person:Person) WHERE ID(person)= { id } RETURN person { id: '66' }
I20150921-01:17:13.599(0)? Exception in callback of async function: Error: [Meteor.neo4j.run]: [500]
I20150921-01:17:13.599(0)? at packages/ostrio:neo4jreactivity/driver.coffee:659:21
I20150921-01:17:13.599(0)? at packages/ostrio:neo4jreactivity/driver.coffee:7:12
I20150921-01:17:13.599(0)? at runWithEnvironment (packages/meteor/dynamics_nodejs.js:108:1)
@dr-dimitru Check out the api branch of my fork at https://github.com/blackslate/ostrio-neo4jdriver.git
You'll see that I am working on a tool to display all the commands for the driver:
- Syntax
- Try it yourself [ Execute ] button
- Output from the command
For now, only Neo4jDB() is complete.
Now that you have added all the new commands, I'll have plenty more work to do.
Note that the failure to throw exceptions means that the client cannot tell if the Neo4jDB() command succeeded or not
- On the left, you have an inspector showing you the nodes and edges in your database, so that you can find the values you need for your custom queries.
- Next to that, you have a list of all the commands
- On the right, you see your description of the chosen command at the top, and below that you can test the chosen command and see the result.
As I know till end of this year will be published 3.x within Bolt protocol - which will bring major changes.
If you are expecting issue with fibers (Error: Cannot find module 'fibers'), install version with postfix -fiber, like: ostrio:neo4jdriver@1.0.2-fiber
Also: VeliovGroup/ostrio-neo4jdriver#26
So, just use ostrio:neo4jdriver@1.0.2 version, without -fiber
- API Explorer and practicality
- As far as I can see, creating demo for batch and transaction requires multiple steps. This is requires more effort than I currently believe it be worth.
- There are many sub-cases for Neo4jNodes, Neo4jRelationships and Neo4jTransaction that will require a considerable amount of work to implement
- I'm using this version of your driver:
$ git checkout dev
Switched to branch 'dev'
Your branch is up-to-date with 'origin/dev'.
$ git log --oneline
fd663f4 readme.md
d6ed58a Add known issues
fdab9f8 UPD logo, add min.version
e0b6f9d logo
a63753b v1.0.2-fiber
Can you install my API Explorer and:
- Go to the db.index.create page
- Create an index, for example, on Person ["name"]
- Go to db.index.get
- Enter "Person" (without the quotes) and click Execute, to see the index you just created
- Leave the Label field empty, or deselect its checkbox and click Execute again
- Do you see the Person|name index this time?
I believe it should give a possibility to type-in methods and execute them.
I'm not sure how you would implement this, since the client needs to use Meteor.call(...) to get the server to execute the typed-in method. Different methods produce different results (cursor, objects of different sorts, array, ...) and some require quite complex arguments. Getting the server code to recognize all of these would require a a complex switch system.
Perhaps you could explain your ideas in more detail, so that I can see how they could be workable.
simpler... than [to] predefine everything
One very good reason to predefine everything is that a newcomer can see at a glance what is possible. If s/he has to type in methods manually, then it assumes that s/he already knows the methods and their syntax, in which case, why bother using an API Explorer?
