NoSQL and SQL

 

The debate SQL vs NoSQL is very interesting and controversial now days. There are many exciting new findings and each of the both camps has its advantages.

We believe that the biggest advantage is be able
to combine SQL and NoSQL approaches and use the best the two worlds.

 

LightLink offers a seamless support for JSON data types from in-browser JavaScript to the server-side.

Developers simply create their JSON object and use it as a parameter. On the server side this objects can be and/or stored to (retrieved from) the database as native data types.

SELECT
  ID, NAME, PRICE, DATE, 
  UNSTRUCTURED_DATA AS "(json)UNSTRUCTURED_DATA"
FROM TEST_LIST

 

Note UNSTRUCTURED_DATA AS "(json)UNSTRUCTURED_DATA" indicating to handle UNSTRUCTURED_DATA column as JSON type. If the database version does not supports JSON columns natively, a greaceful fallback to BOLB/TEXT is used.


Update example :

UPDATE
  TEST_LIST
SET
  UNSTRUCTURED_DATA =:(json)p.UNSTRUCTURED_DATA 
WHERE 
  ID=:(number)p.ID

 

 

NoSQL  =  Not Only SQL 

So, let’s explain NoSQL as Not Only SQL and see what NoSQL-related features most popular databases offer today:

 

PostgreSQL :

http://www.linuxjournal.com/content/postgresql-nosql-database

http://info.enterprisedb.com/rs/enterprisedb/images/EDB_White_Paper_Using_the_NoSQL_Features_in_Postgres.pdf

Oracle:
https://docs.oracle.com/database/121/ADXDB/json.htm#ADXDB6246

MySQL :

https://dev.mysql.com/doc/refman/5.7/en/json.html

MS SQL:

https://msdn.microsoft.com/en-us/library/dn921882.aspx

In contrast to exclusive NoSQL databases like MongoDB you still use SQL as a query format, but take advantage of SQL environment combined with main NoSQL features :

- semi-structured and unstructured data,

- filtering and indexes by data in JSON objects,

- key-value, document store, etc..