New answers tagged

7

"NoSQL" doesn't consistently refer to any one concept, because it's a marketing term, not a technical one. See for instance my answer on the DBA site. I think you have to look at the historical development of the term, rather than its face meaning: early databases were many and varied. Relational databases in their theoretical purity never actually ...


2

Yes, that's how I understand and use the terms. Non-relational is actually a slightly better term for this mainly because SQL is a language, not a data storage architecture. I feel both terms are flawed, though, in that they describe what something is not instead of what it is. There are alternate query languages for relation DBs. For example Google has ...


2

Unfortunately, yes, they largely do. The common point of most systems that call themselves "NoSQL" is not so much that they don't have a structured query language (many do have query languages, and some of them aren't actually all that different from SQL), but that they don't enforce a rigid schema on the data they contain. Why exactly the term '...


0

For adding Orestis's opinion, IMHO, how about not saving all the events in an array in a document, but just having a single event and updating it because CDC can capture all the update event using oplog even though it will be overwritten immediately by another event. If it is possible, we don't have to manage additional processes to delete published events ...


2

I was thinking the JSON document would also have the key so this would make it redundant. Which attribute is the key? How is your database supposed to know? Short of indexing all of them, how is it going to efficiently retrieve any, one, JSON document? One of the most important factors that will govern how you store any data is how you intended to retrieve ...


2

From DocBrown's advice I've learned that a generated column could be defined off of an attribute from the JSON document. Here is the table creation sql: CREATE TABLE `test_run` ( `start_time` TIMESTAMP GENERATED ALWAYS AS (`json_doc` ->> '$.start_time') STORED KEY NOT NULL PRIMARY KEY, `json_doc` JSON NOT NULL ); Note our data gets more ...


Top 50 recent answers are included