On Jun 15, 2014, at 1:58 PM, Josh Berkus j...@agliodbs.com wrote:
In other words, what I'm saying is: I don't think there's an existing,
poplular syntax we could reasonably use.
Okay, I’m good with that. Would be handy to document it in such a way as to
kind of put it forward as a standard.
On 06/10/2014 02:46 PM, David E. Wheeler wrote:
On Jun 10, 2014, at 12:06 PM, Oleg Bartunov obartu...@gmail.com wrote:
we have many other tasks than guessing the language name.
jsquery is just an extension, which we invent to test our indexing
stuff. Eventually, it grew out. I think we'll
On 06/15/2014 04:58 PM, Josh Berkus wrote:
I've been poking at the various json-query syntaxes you forwarded, and
none of them really work for the actual jsquery features. Also, the
existing syntax has the advantage of being *simple*, relatively
speaking, and reasonably similar to JSONPATH.
On Jun 6, 2014, at 3:50 PM, Josh Berkus j...@agliodbs.com wrote:
Maybe we should call it jsonesque ;-)
I propose JOQL: JSON Object Query Language.
Best,
David
PS: JAQL sounds better, but [already exists](http://code.google.com/p/jaql/).
signature.asc
Description: Message signed with
People,
we have many other tasks than guessing the language name.
jsquery is just an extension, which we invent to test our indexing
stuff. Eventually, it grew out. I think we'll think on better name
if developers agree to have it in core. For now, jsquery is good
enough to us.
jsquery name
The closest problem we have is jsonb statistics (lack of, actually) ,
which prevents use of all the power of jsquery. I hope Jan Urbański
could work on this.
Oleg
On Tue, Jun 10, 2014 at 11:06 PM, Oleg Bartunov obartu...@gmail.com wrote:
People,
we have many other tasks than guessing the
On Jun 10, 2014, at 12:06 PM, Oleg Bartunov obartu...@gmail.com wrote:
we have many other tasks than guessing the language name.
jsquery is just an extension, which we invent to test our indexing
stuff. Eventually, it grew out. I think we'll think on better name
if developers agree to have
Jsquery - is QUERY language, JsonPath - is language to EXTRACT json parts.
On Fri, Jun 6, 2014 at 4:34 AM, David E. Wheeler da...@justatheory.com wrote:
On Jun 5, 2014, at 5:25 PM, Andrew Dunstan and...@dunslane.net wrote:
My understanding is that it's meant to be analogous to tsquery.
At
On Jun 6, 2014, at 6:54 AM, Oleg Bartunov obartu...@gmail.com wrote:
Jsquery - is QUERY language, JsonPath - is language to EXTRACT json parts.
Sure, but could we not potentially build on its syntax, instead of building a
new one? I’m not saying we *should*, but if we don’t, I think there
On 06/06/2014 09:12 AM, David E. Wheeler wrote:
On Jun 6, 2014, at 6:54 AM, Oleg Bartunov obartu...@gmail.com wrote:
Jsquery - is QUERY language, JsonPath - is language to EXTRACT json parts.
Sure, but could we not potentially build on its syntax, instead of building a
new one? I’m not
On Jun 6, 2014, at 12:51 PM, Josh Berkus j...@agliodbs.com wrote:
* [JAQL](https://code.google.com/p/jaql/): Too different from SQL
* [JSONPath](http://goessner.net/articles/JsonPath/): Too verbose
I don't agree with the too verbose, but lacking AND|OR is pretty crippling.
I had enough
On 06/06/2014 03:23 PM, David E. Wheeler wrote:
On Jun 6, 2014, at 12:51 PM, Josh Berkus j...@agliodbs.com wrote:
Well, I'd also say that we don't care about syntaxes which are not
already popular. There's no point in being compatible with something
nobody uses. How many of the above have
On 06/05/2014 08:08 PM, David E. Wheeler wrote:
Oleg, Teodor, and Hackers:
Love what you’re doing with JSQuery. I’m curious, though, whether you
considered adopting an existing syntax, such as JSONPath.
http://goessner.net/articles/JsonPath/
Might be easier for people to pick up and use.
On Jun 5, 2014, at 5:25 PM, Andrew Dunstan and...@dunslane.net wrote:
My understanding is that it's meant to be analogous to tsquery.
At first glance, JsonPath doesn't seem to support AND and OR operators, which
would make it rather less expressive than I gather JSQuery is meant to be.
14 matches
Mail list logo
