neo4j - @Query result type different between ImpermanentGraphDatabase and SpringCypherRestGraphDatabase? -

-

i using @query annotation on repository interface method retrieve list of nodes contained in path.

if switch impermanentgraphdatabase springcypherrestgraphdatabase, having errors while parsing results because type returned query different :

context :

  • using sdn 3.3.0.release , neo4j 2.1.7
  • code used in junit test
  • my graph : (t:type1)-[:has_key]->(:key)-[:next]->(:key)-[:next]->(:key)-[:next]->.... , on (yeah, sounds linkedlist ^^)

  • the query "i want keys associated type" used path query :

    match (key:key)<-[:has_key]-(:type1 {typeid :{0}}), p=(key)-[:next*]->(:key) return nodes(p) order length(p) desc limit 1

using impermanentgraphdatabase :

  • my query returns iterable<iterable<object>> , have cast "object" inside nodeentity using neo4joperations.convert(...) method because objects of type nodeproxy.

using springcypherrestgraphdatabase :

  • my query returns iterable<iterable<map<string, string>>>, , map contains property name of node key , corresponding value map entry value.

why there such implementation difference ? shouldn't expect same behaviour regardless of database service implementation ?

thank you.

p.s. : way, tried achieve same goal using traversaldescription: works , same traversaldescription works on both database implementations


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more