![]() ![]() As you see, these were hard and relentless times.Īnd then time moved on and people started buying things on the Internet (whatever the Internet is – I think it is some kind of glorified, stylish version of punched cards) and stuff such as Facebook and Google came around. (And following rules is something I am good at? Again, I wonder how I ended up in this business.) Like, a price had to be a number of some kind, with a value 0 or higher and some other restrictions. And not only that, but stuff that was stored had some kind of value, somehow, which meant it had to follow certain rules. The little that would fit was the really important stuff, like price, amount in stock, customer names, billing addresses and such – and nothing else. Anyway, no one in their right mind would have considered string pictures of cute felines as something to be on a computer, or actually stuff to be stored in a database. Also, they were as powerful as a slide ruler, except they were fed with punch cards (and probably powered by steam). When the sad old git who is writing this stuff started working in this industry, which I think was during the Harding administration, computers were rare, expensive, handled only by experts (so how I got to work with them is a mystery) and built from Lego bricks, Meccano and pieces of solid gold (to keep up the price). Using JSON for unstructured data is rather neat, and JSON is even standardized (see ). (For more detail on JSON functions, including sample data and queries, check out this white paper: Flexible Data Modeling with MariaDB Server: JSON Functions.) In my mind that means that mixing relational data with unstructured data is what we really want. So to begin, Why do we need JSON? Or to put it differently, why do we not store all data in JSON? Well, the reason as I see it is that some data we work with really is best treated as schemaless, whereas other data really should be handled more strictly in a schema. We’ll also look at some other MariaDB features that are useful for JSON processing. Here I’ll describe JSON and the use cases for it, as well as the MariaDB JSON functions and their uses. There are a few good reasons why a JSON datatype hasn’t been implemented, but one is that there are just not many advantages to that, as JSON is a text-based format. ![]() JSON is fast becoming the standard format for data interchange and for unstructured data, and MariaDB Platform (in fact, all MariaDB versions 10.2 and later) include a range of JSON supporting functions. We’ve brought the details up-to-date with the latest MariaDB releases. This is an update of the popular post on JSON with MariaDB 10.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |