Comments on: JsonSQL: JSON parser, SQL style

By: oliverclevont

oliverclevont — Fri, 18 Jan 2008 10:59:10 +0000

Should provide an abstraction that also caters to the upcoming Offline browser storage API.

By: nextdb

nextdb — Thu, 17 Jan 2008 13:31:16 +0000

An interesting thing to consider is how you go “the other way”. That is, how do you produce JSON Objects that represent convenient “views” of data structured in a relational database. NextQuery is the query language of http://nextdb.net that allows you to “reshape” the results of the relational query into JSON Objects. Responding to the earlier post, that said “…there are some strong conceptual mismatches between SQL and JSON”, NextQuery addresses some of these concerns, and allows for a very natural bridge from the relational model to JSON.

By: KrisKowal

KrisKowal — Wed, 16 Jan 2008 18:38:23 +0000

I like the idea of using a DSL for queries. For the joy of the exercise alone, here's the equivalent in Chiron JavaScript: include('base.js'); where(arr, get('id').then(gt(4))).each(get('age')).sorted() I'd love to further explore translating queries in a DSL into functions that operate on JavaScript objects. Perhaps this is a good place for partial application: query(dsl, array of objects) -> array of objects query(dsl) -> Query reusable compiled query query(dsl)(array of objects) -> array of objects

By: kadnan

kadnan — Wed, 16 Jan 2008 17:14:11 +0000

Awesome stuff. Hope author would provide DML feature as well.

By: kriszyp

kriszyp — Wed, 16 Jan 2008 16:58:56 +0000

While I think that these other approaches are generally better for JSON, I don’t want to be too negative, jsonSQL is not without merit. There may be those out there for whom SQL is their most familiar language, and I think that this might benefit them.

By: sandrejev

sandrejev — Wed, 16 Jan 2008 15:50:56 +0000

Writing it in jquery or in prototype (or in whatever great framework out there) is not so bad either:

var arr = [
{id: 1, age: 45},
{id: 2, age: 17},
{id: 3, age: 22},
{id: 4, age: 31},
{id: 5, age: 14},
{id: 6, age: 28},
{id: 7, age: 15}];

$.map(arr, function(r){ if(r.id > 4) return r.age }).sort()

By: kriszyp

kriszyp — Wed, 16 Jan 2008 14:03:28 +0000

This is a reasonable idea, and good job with implementing it, but there are some strong conceptual mismatches between SQL and JSON. JSON has an object structure, not a flat table structure. For this reason, object databases have used OQL (object query language) which looks similiar SQL, but is designed to meet the different data structure needs of object structures. However, your jsonSQL actually looks more like OQL than SQL (although of course I understand the marketability of “SQL” over “OQL”).
However, for the purpose of querying JSON object-structured data, I believe JsonPath generally provides a much cleaner, more compact, and more appropriate syntax for querying JSON data.

By: Aaron

Aaron — Wed, 16 Jan 2008 13:53:27 +0000

Love the idea! Seems natural to use sql for json too.

By: JohnP

JohnP — Wed, 16 Jan 2008 13:15:20 +0000

Very dangerous!

By: dcrec1

dcrec1 — Wed, 16 Jan 2008 12:45:53 +0000

Very good, impressive!