JCR SQL2 query by node identifier?

[jonathandfields]

I hope that I have not missed something obvious, but it is possible to include a node's internal identifier (Node.getIdentifier()) in a JCR SQL2 query condition? I don't see it in the spec or documentation, and have tried a few things like [mode:uuid] but so far no luck. If not, I'm assuming that the equivalent would be to make the node type mix:referenceable, and then include jcr:uuid in the query....

Thanks, Jon.

[rhauch]

Hmm... You've not missed something obvious, but I think we have and the JSR-283 Expert Group has, too. I've submitted a question to the rest of the JSR-333 Expert Group to see whether they have any ideas. Worst case, we can either come up with a ModeShape-specific pseudo-column or change the behavior of the "jcr:uuid" column such that it appears on every record.

In the mean time, can you please log this as an issue? If you have a preferred approach, please describe it in a comment on the issue.

Thanks, Jonathan!

[jonathandfields]

MODE-1671 created.

I discovered this trying to find a way to retrieve a node by identifier using the REST service. Therefore I've also logged MODE-1672 which would satisfy that immediate need.

Thanks!

Jon

[rhauch]

Thanks for logging those, Jonathan. I've targeted MODE-1671 to 3.1, but we'll try to get MODE-1672 into 3.0.0.CR2.

[jonathandfields]

Excellent, thank you.

[bwallis42]

I've just hit the problem of MODE-1671, no way to query using the node identifier. I see that the ticket is marked for resolution in 3.2. Is it possible that this might make it into 3.1?

thanks.

[rhauch]

I'ved moved MODE-1671 back into 3.1 so that we look for workarounds and evaluate potential approaches. Based upon those results, we'll re-evaluate whether we can fit this into 3.1 (which is already late). If we can't fit it, then we'll move back to 3.2.