couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Eberlei <>
Subject Re: UnQL
Date Fri, 26 Aug 2011 11:55:26 GMT
UnQL written as string is just one "representation", a json variant that
compiles to the same AST would probably be very cool.

Regarding the fulltext search, JCR defines an SQL like language aswell that
looks very much like UnQL and it contains a "function" which does
fulltext-search working somewhat like MySQLs MATCH AGAINST. This could
easily be a CouchDB unql fn if couch ever got native fulltext search.

But this is both beside the point:

What i miss is a discussion about UnQL in CouchDB at all. What are the plans
and the roadmap.

On Fri, Aug 26, 2011 at 1:16 PM, Andrew Stuart (SuperCoders) <> wrote:

> Off topic, but I think an official solution to full text search should have
> been a higher priority than unql.
> as
> On 26/08/2011, at 5:21 PM, Mark Hahn wrote:
> I'm kind of surprised that there has been no mention of UnQL on this
> mailing
> list, especially since the creator of couch was one of the two "inventors".
> Also UnQL adoption would obviously have a big impact on CouchDB.
> I'll throw out my 2 bits, fwiw ...
> I haven't got any good arguments yet, but I feel having a text-based
> SQL-like language for couch would be a big step backwards.  I do feel couch
> needs to expand it's query capabilities, and I trust it will.  But I would
> imagine the solution to be more modern than the old process of building up
> a
> query text string and sending it off.  Maybe it is just an emotional
> reaction after all the years of hating the impedance mismatch of the SQL
> language and all the languages I had to use it in.
> --
> Message  protected by MailGuard: e-mail anti-virus, anti-spam and content
> filtering.http://www.**<>
> Click here to report this message as spam:
> 5QlJAt26DID3kD3ID9wn90/2.412<>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message