timetree | General persistence transformations

The procedure apoc.cypher.run can only execute read queries. Creating/updating/deleting nodes is not allowed with it.

the propType define only the types, not the actual value. if you export the function export const fetchData just import it from your component file, and use it:

The time parameter is a millisecond timestamp, or milliseconds elapsed since the UNIX epoch, which is an extremely common means of storing time-related data, you can find this in use in nearly every digital system.

The timestamp cited here represents "2016-05-19 12:06:07". The timetree built starts from a root (this is a modeling convenience), and then its child is the year (2016) followed by the month (5), then the date of the month (19). Looks like it didn't automatically create any nodes for time resolutions beyond that.

Keep in mind that now that Neo4j has native temporal values that you can use in Cypher and store as properties (as well as index), time trees are going to be less useful, as you can always do index lookups on indexed temporal properties.

There are still some cases where time trees can still be very useful, however, such as when you're searching for events that happened within some unit of time that disregards its parent units...such as finding events that happened on Mondays regardless of month, or on Januaries regardless of year, and so forth.

Even without the availability of async/await, you should very rarely need to use new Promise(). If you're using it a lot, it's typically a code smell.

The whole point of async/await is that it allows you to avoid a lot of the situations where you would otherwise need to work with promises explicitly.

So if it's supported in the environment you're targeting (Internet Explorer does not support async/await) or you're using a transpiler, go ahead and use it anywhere you can. That's what it's for.

Bear in mind that this is pointless:

It is because the configuration class redefines some beans already automatically configured by Spring boot (here the Session).

So spring injection does not know how to choose between the 2. Removing the getSession() should help.

A second thing is that your SessionFactory has to use the embedded DB setup in the graphDatabaseService() method. For this, configure an embedded driver with the existing database.

Summary config that should work fine for you :

The problem with your first query is that you're not doing anything with the results of the timetree query. It is literally just wasting cycles and bloating up the built up rows with data that's not even used.

You need to take the :Tweet nodes returned from your timetree query and include them into the next part of your query.

In order to have the Timetree module loaded, you will need to add those lines to the configuration :

First off - good work on putting all the code there, it made life a lot easier!

I believe the problem here is two fold: the tstamp variable you have is of type: ICypherFluentQuery (I'm using '?' to represent the anonymous type you're creating) - so you need to actually get the results to get any response. Until you call .Results you don't actually execute the query.

Typically, I like to create the query as you have and then execute after: