Hi, What is your use case?
I think the fact that MySQL can generate the "explain plan" in JSON format isn't really a good reason why H2 needs to support JSON. But I do agree that JSON is important, similar than XML. Many web applications use JSON and some NoSQL databases support it (for example MongoDB). However, JSON in a relational database is something different. See also http://stackoverflow.com/questions/3564024/storing-data-in-mysql-as-json If you use a relational database, I assume you want to use a solution that works not just in one database but in a way that is portable to many databases. For example storing the JSON as text. Maybe you want also want the ability to create indexes (similar to MongoDB). Luckily, you can do that already by using user defined functions. Similar to the XML functions in H2, that can be ported to other databases. I don't think supporting a JSON data type is all that important (similar to an XML data type). Just use VARCHAR or CLOB. I view JSON as similar important than XML. But so far there were no actual use cases or questions about XML support on the H2 group. So I assume people don't have a problem that needs to be solved. So again, as for JSON, what is your use case? What problem do you need to solve? Regards, Thomas On Fri, Jul 19, 2013 at 10:49 PM, Rami Ojares <[email protected]> wrote: > I followed the first link and found a list of 4 reasons. > > 1. "MQL is great ... " > Blah blah blah > 2. "RDBMS-es are great solutions for storing and structuring data" > Yeah well that's not a reason for MQL > 3. "SQL ... is completely unsuitable and inappropriate for AJAX web > applications (for many, too many reasons)" > Would have been nice to hear even one reason ... > 4. "Traditional solutions to data access for AJAX web applications rely on > special purpose webservices, which have to be reinvented for every single > web application" > H2 has an undocumented network protocol that handles traffic between > client and server. > Users are supposed to use that protocol through jdbc classes (or they can > use Jaqu if they want). > Then there is the question of query language. > H2 has decided to implement sql in such a fashion that it tries to be > compatible with other database products. > > Now do you want to define a new network protocol, query language or both? > > If network protocol then I would say that the first step should be to > define a public specification of the H2 protocol. > If JSON seems like a good way to define such protocol, fine. > > If query language then is MQL more expressive than SQL? > I mean can you make queries with MQL that you can't with SQL? > I would be surprised if that was the case. > > - Rami > > > On 19.07.2013 14:19, Anthony wrote: > > The following points may worth a lookin. > > https://code.google.com/p/mql-to-sql/ > > > http://slashdot.org/topic/datacenter/why-database-administrators-should-consider-json/ > > > > On Friday, July 19, 2013 11:31:21 AM UTC+1, Rami Ojares wrote: >> >> Why would someone want json support for a database? What does it mean? If >> you want to query data contained inside json fragment (or xml) decompose it >> to relations and voila. >> On Jul 19, 2013 12:51 PM, "Anthony" <[email protected]> wrote: >> >>> I notice that JSON support is way down on priority 2 list. Surely this >>> should be placed higher up the list. >>> A few of the main dbms have already implemented some form of json >>> support for example >>> >>> MariaDB / MySQL there EXPLAIN feature in version 5.6 >>> https://blog.mozilla.org/**it/2013/01/22/new-explain-** >>> features-in-mysql-5-6-**formatjson-actually-adds-more-**information/<https://blog.mozilla.org/it/2013/01/22/new-explain-features-in-mysql-5-6-formatjson-actually-adds-more-information/> >>> >>> PostgreSQL 9.3 http://wiki.postgresql.**org/wiki/What's_new_in_** >>> PostgreSQL_9.3#JSON:_**Additional_functionality<http://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.3#JSON:_Additional_functionality> >>> >>> as well s the usual OODBs such as CounchDB, MongoDB (BSON), Oracle >>> NoSQl DB 2.0, Apache Cassandra etc >>> >>> As more developer are implementing some form of ajax web base systems >>> such a feature can only improve our productivity. >>> >>> Any thought on the will be appreciated. >>> >>> Anthony >>> >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "H2 Database" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to h2-database...@**googlegroups.com. >>> To post to this group, send email to [email protected]. >>> Visit this group at >>> http://groups.google.com/**group/h2-database<http://groups.google.com/group/h2-database> >>> . >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
