On 5/5/08, Emil Eifrem <[EMAIL PROTECTED]> wrote: > It seems weird to me that an attribute named "id" would be optional,
The system relies heavily on MusicBrainz, but it's possible that some artists from a Last.fm top list or similar don't have a known MBID mapping (yet). > How do you get access to this instance? Ah, dependency resolution. > Without theoretizing too much, there are roughly three ways you can go > about this: Thanks for taking the time to endulge me with these Neo-unrelated design issues. I had started with a singleton only to find that it caused a Transaction to be started before Neo -> b0rked. While it's always possible to make something that works by accident, having terminology that describe it makes thinking about it much less painful. For the record, solution 2 (IoC) was the one of my liking. > Hmm, it strikes me that our current indexes may not work correctly > with array values. Hashcode and equality on arrays are by default > based on the actual array *instance* in Java -- not on the underlying > elements in the array. So we would need to detect that someone is > passing in an array and then use Arrays.hashCode() and > Arrays.equals(). I can confirm that using long[] as an index value doesn't work -- each long[] is treated as unique even though the content is the same. I'm not sure if this is what you want or not, but since arrays are supported neo values I kind of assumed it would work is index values as well. For now uuid.getLeastSignificantBits() is good enough. Philip _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
