#Document Data Model (NoSQL)

Before we start talking about databases and different data models that exist, first we'd better talk about what a database is and how to use it.

A database is an organized collection of data stored and accessed electronically. It is used to store and retrieve structured, semi-structured, or raw data which is often related to a theme or activity.

At the heart of every database lies at least one model used to describe its data. And depending on the model it is based on, a database may have slightly different characteristics and store different types of data.

To write, retrieve, modify, sort, transform or print the information from the database, a software called Database Management System (DBMS) is used.

The size, capacity, and performance of databases and their respective DBMS have increased by several orders of magnitude. It has been made possible by technological advances in various areas, such as processors, computer memory, computer storage, and computer networks. In general, the development of database technology can be divided into four generations based on the data models or structure: navigational, relational, object and post-relational.

Hello all,

I'm "playing" a little bit with IRIS as document database, as it seems really simple to use.

So far, creating a database and inserting documents is fine. Creating a Property so it can be indexed seems very useful and it works well when this property is created at the very beginning. But here my "problem": whenever a new property is added, how can the values be recalculated and inserted, so indices can be correctly updated?

hello, I had build a DocDB referring the code from here: https://community.intersystems.com/post/how-can-i-create-properties-docd...

Here are the structure of the json Documents I have added in my database called 'Orders'.

I have an application with maps that render and edit geographic data in a some layers using KML - geo data represented into XML file with layers, polygnons, points and metadata associated with it. Some maps are in GeoJSON too.

Is it DocDB the better option?

Hello,

I have imported my data with the following code (%DocDB).

set filename = "/home/student/Dokumente/convertcsv.json"

IF $SYSTEM.DocDB.Exists("Fitabase1") {

SET db = ##class(%DocDB.Database).%GetDatabase("Fitabase1")

}

ELSE {

SET db = ##class(%DocDB.Database).%CreateDatabase("Fitabase1")

}

set arr = ##class(%DynamicAbstractObject).%FromJSON(filename)

SET jstring = arr.%ToJSON()

//SET doccount = db.%Size()

DO db.%FromJSON(jstring)

Does anybody know how can I get the DocumentId property from a DocDM repository using SQL?. So far my SQL is like this:

SELECT name,email,gender FROM JSON_TABLE(
'person',
'$' COLUMNS(
name VARCHAR(100) PATH '$.name',
email VARCHAR(100) PATH '$.email',
gender VARCHAR(2) PATH '$.gender'
)
)

Thanks!

Presenter: Stefan Wittmann
Task: Take advantage of the NoSQL paradigm without adding another tool
Approach: Provide sample use cases that are an excellent fit for InterSystems’ new document data model

Description: Designing applications always requires you to make assumptions about your data model. Come to this session to learn how you can effectively handle the cases where you have to rapidly evolve your model. We will also discuss other use cases that are an awesome fit for the flexible document data model.

Problem: I’ve observed the NoSQL landscape and like the direction, but I have no use-case that fits and I do not want to add yet another tool.

Solution: InterSystems now has support for a well integrated document data model that brings the NoSQL paradigm to the enterprise within your current stack.

Content related to this session, including slides, video and additional learning content can be found here.