[Neo4j] Index returns all nodes for value="undefined"!
We're seeing this crazy behavior where our exact index is returning all nodes if we pass a lookup value of "undefined"! E.g.: http://localhost:7474/db/data/index/node/nodes/username/undefined Is this a bug in Neo4j / REST API? Or is this a symptom of some bug we have in our own code? It could very well be our code, since we're using JS, which turns undefined values into the string "undefined" if you try to add it to a string (definitely a wtfjs candidate), but I wanted to see if others are seeing this in Neo4j too! Thanks, Aseem ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Index returns all nodes for value="undefined"!
No, there's no such "undefined" constant which will return everything. It definitely sounds like a JavaScript issue, and that it turns nulls into "undefined". And perhaps your code which tries to index null values. 2011/7/16 Aseem Kishore > We're seeing this crazy behavior where our exact index is returning all > nodes if we pass a lookup value of "undefined"! E.g.: > > http://localhost:7474/db/data/index/node/nodes/username/undefined > > Is this a bug in Neo4j / REST API? Or is this a symptom of some bug we have > in our own code? > > It could very well be our code, since we're using JS, which turns undefined > values into the string "undefined" if you try to add it to a string > (definitely a wtfjs candidate), but I wanted to see if others are seeing > this in Neo4j too! > > Thanks, > > Aseem > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [matt...@neotechnology.com] Hacker, Neo Technology www.neotechnology.com ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Index returns all nodes for value="undefined"!
Perhaps it is also an issue of your REST-client? If the value when rendered as part of a string evaluates to the empty string the resulting URL would be the same as the one that retrieves all nodes. i.e. http://localhost:7474/db/data/index/node/nodes/username Just an idea, could you verify the REST url that is used? Am 17.07.2011 um 17:06 schrieb Mattias Persson: > No, there's no such "undefined" constant which will return everything. It > definitely sounds like a JavaScript issue, and that it turns nulls into > "undefined". And perhaps your code which tries to index null values. > > 2011/7/16 Aseem Kishore > >> We're seeing this crazy behavior where our exact index is returning all >> nodes if we pass a lookup value of "undefined"! E.g.: >> >> http://localhost:7474/db/data/index/node/nodes/username/undefined >> >> Is this a bug in Neo4j / REST API? Or is this a symptom of some bug we have >> in our own code? >> >> It could very well be our code, since we're using JS, which turns undefined >> values into the string "undefined" if you try to add it to a string >> (definitely a wtfjs candidate), but I wanted to see if others are seeing >> this in Neo4j too! >> >> Thanks, >> >> Aseem >> ___ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user >> > > > > -- > Mattias Persson, [matt...@neotechnology.com] > Hacker, Neo Technology > www.neotechnology.com > ___ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user ___ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
Re: [Neo4j] Index returns all nodes for value="undefined"!
Thanks guys. This must have been a bug on our end then, and it must have
been transient, because the returned nodes were old ones. We added an
explicit not {null, undefined or empty string} check a while back, so that
must have saved us.
Aseem
On Sun, Jul 17, 2011 at 1:00 PM, Michael Hunger <
michael.hun...@neotechnology.com> wrote:
> Perhaps it is also an issue of your REST-client? If the value when rendered
> as part of a string evaluates to the
> empty string the resulting URL would be the same as the one that retrieves
> all nodes.
>
> i.e. http://localhost:7474/db/data/index/node/nodes/username
>
> Just an idea, could you verify the REST url that is used?
>
>
> Am 17.07.2011 um 17:06 schrieb Mattias Persson:
>
> > No, there's no such "undefined" constant which will return everything. It
> > definitely sounds like a JavaScript issue, and that it turns nulls into
> > "undefined". And perhaps your code which tries to index null values.
> >
> > 2011/7/16 Aseem Kishore
> >
> >> We're seeing this crazy behavior where our exact index is returning all
> >> nodes if we pass a lookup value of "undefined"! E.g.:
> >>
> >> http://localhost:7474/db/data/index/node/nodes/username/undefined
> >>
> >> Is this a bug in Neo4j / REST API? Or is this a symptom of some bug we
> have
> >> in our own code?
> >>
> >> It could very well be our code, since we're using JS, which turns
> undefined
> >> values into the string "undefined" if you try to add it to a string
> >> (definitely a wtfjs candidate), but I wanted to see if others are seeing
> >> this in Neo4j too!
> >>
> >> Thanks,
> >>
> >> Aseem
> >> ___
> >> Neo4j mailing list
> >> User@lists.neo4j.org
> >> https://lists.neo4j.org/mailman/listinfo/user
> >>
> >
> >
> >
> > --
> > Mattias Persson, [matt...@neotechnology.com]
> > Hacker, Neo Technology
> > www.neotechnology.com
> > ___
> > Neo4j mailing list
> > User@lists.neo4j.org
> > https://lists.neo4j.org/mailman/listinfo/user
>
> ___
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
>
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
