Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Alex Sheluchin
    @sheluchin
    I'm looking at combining redisgraph-py with https://github.com/tobgu/pyrsistent to create a functional and immutable wrapper around graphs, nodes, and edges. Does anyone have any opinion about this?
    Dave Nielsen
    @dnielsen
    Hi Alex, we don't have experience with pyrsistent. But I am intrigued with idea. What is a common use case where a Redis developer would need a persistent data structure?
    Alex Sheluchin
    @sheluchin
    @dnielsen The general idea is to use persistent data structures along with a functional programming style. The goal would be to reduce potential side-effects and the amount of mutable state that developers need to keep track of when working with different elements in Python. I think there could be some upside to structural data sharing as well (which pyrsistent implements), where multiple instances of a graph would share all the common immutable elements.
    Dave Nielsen
    @dnielsen
    I see. Not something I've thought of, but I see how it could be useful. Perhaps it could help data scientists with reproducibility too. Why not give it a try? I can help share it online if you do.
    Pieter Cailliau
    @K-Jo
    Tony André Haugen
    @t0nyandre
    I have had a few problem using the redisgraph-go package because I can't access the results from a query. I have forked the package and done some local hacks (added functions to retrieve the results and headers). Will there be any releases before Redis Day London? :P
    DvirDukhan
    @DvirDukhan
    Can you specify your redisgraph-go and RedisGraph versions?
    Tony André Haugen
    @t0nyandre
    Yeah, sure. I am using the latest Docker container at https://hub.docker.com/r/redislabs/redisgraph for my redisgraph and I am using redisgraph/redisgraph-go v2.0.0
    Tony André Haugen
    @t0nyandre

    One thing we should try to mimic from the neo4j package is that when you query the results get returned:

    data,  err := rg.Query(`MATCH(u:user) RETURN u`)

    That would make it easier to use. I might be missing something, but I can't find a way to get the results without "pretty printing" it to the console. You could also return the headers if that deems necessary.

    Tony André Haugen
    @t0nyandre
    @DvirDukhan Right now you get the *QueryResult but with no way of accessing results because it's not exported. I see two ways of doing this. Export the results or add a function to get the results from the *QueryResult
    Roi Lipman
    @swilly22
    @t0nyandre , I'll try to introduce an interface similar to https://github.com/neo4j/neo4j-go-driver over the next couple of days
    Tony André Haugen
    @t0nyandre
    Nice @swilly22 .. I've been making my own minimal package now because I got stuck with not being able to use the results properly. There is no need for two incomplete ones so I'll rather just help contribute to yours when you push out the changes :)