Hello
This might help you:
http://api.neo4j.org/current/org/neo4j/graphdb/Transaction.html
And I'm not sure if this thread is still valid as reference:
http://www.mail-archive.com/user@lists.neo4j.org/msg03716.html
-
Charles Edward Bedón Cortázar
ITIL Founda
hello list
how to make rolledback a transaction
thanks
cheers.
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Here's what I see in the messages.log when I tried the backup command:
Fri May 20 07:00:24 PDT 2011: Found dead channel [id: 0x3d36acb6, /
127.0.0.1:56110 :> /127.0.0.1:6362], SlaveContext[ID:0, eventIdentifier:0,
[(lucene-index, 15726285), (nioneodb, 38747027)]]
Fri May 20 07:00:24 PDT 2011: Remo
Interesting. That's exactly what we do with our metadata REST API. You can
either use:
/Thingworx/Things/SkynetOverload/Metadata
...or
/Thingworx/Things/SkynetOverload?metadata
...which also allows specification of the content type (text/xml or
application/json) to be independent.
-
Another agreement here. It doesn't even have to be a query parameter - just
identify the compact variant with a different URI.
What would be the caching implications if it were a query parameter? Though
the URI spec says querystring parameters effectively create a new URI, I
think many caches/reve
> what abt rel types, dirs and id's?
>
> Then we can get back subgraphs with full node and rel info via traversers.
Switch back to the non-compact format if you want them.
> and if we go compact we should either ditch whitespace as well or support
> gzipped output.
That's a further optimisatio
Agree with Jim. This fits better as a query parameter vs content type.
- Reply message -
From: "Jim Webber"
Date: Sat, May 21, 2011 6:10 am
Subject: [Neo4j] Compact JSON format for the server
To: "Neo4j user discussions"
Oh, I just thought:
Is the media type really the right place fo
what abt rel types, dirs and id's?
Then we can get back subgraphs with full node and rel info via traversers.
and if we go compact we should either ditch whitespace as well or support
gzipped output.
M
Sent from my iBrick4
Am 21.05.2011 um 12:09 schrieb Jim Webber :
> Oh, I just thought:
>
Oh, I just thought:
Is the media type really the right place for this?
The media type is still (alas) JSON. Perhaps what we're asking for here is the
representation of a different resource (which happens to be smaller).
So instead of negotiating:
Accept: application/json;compact=true
Perhaps
True.
Ditched.
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer
http://www.neo4j.org - Your high performance graph database.
http://
Hi Peter,
If you're going to make it really compact, also ditch the "self" relationship
perhaps.
Jim
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
Hi all,
Tobias and I started to support an additional, more compact JSON format for
the server. basically, upon specifying "application/json;compact=true" as
the accepted format, the returned node representation looks now something
like
GET http://localhost:7474/db/data/node/1
{
"data" : {
The Koans have a section on pattern matching, see:
https://github.com/jimwebber/neo4j-tutorial
Jim
On 20 May 2011, at 18:09, noppanit wrote:
> I'm learning to use PatternRelationship to look for a pattern of
> relationships in the dataset. I was wondering that is there any example? I
> only fou
13 matches
Mail list logo
