For the benefit of those who want to use the Document Database (DocDB) capabilities within InterSystems IRIS, and specifically the REST API it provides, I put together a Postman Collection that provides samples for several basic calls.

For example:

10
0 0 100
Question
Tuan Minh Do · Jul 16, 2018
%DOC with DeepSee

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) 

00
0 2 234

This summer the Database Platforms department here at InterSystems tried out a new approach to our internship program.  We hired 10 bright students from some of the top colleges in the US and gave them the autonomy to create their own projects which would show off some of the new features of the InterSystems IRIS Data Platform.  The team consisting of Ruchi Asthana, Nathaniel Brennan, and Zhe “Lily” Wang used this opportunity to develop a smart review analysis engine, which they named Lumière.   As they explain:

20
0 0 333

NewBie's Corner Session 29 Documentation on the Caché/MUMPS Global Structure

Welcome to NewBie's Corner, a weekly or biweekly post covering basic Caché Material.

This post contains several links to very good documentation of the Caché Globals Structure.

Like I said, "Perhaps the most difficult concept in Caché/MUMPS is its Global Structure."

 

universalNoSQL.pdf - http://mgateway.com/docs/universalNoSQL.pdf

00
0 6 308

Introduction

The field test of Caché 2016.2 has been available for quite some time and I would like to focus on one of the substantial features that is new in this version: the document data model. This model is a natural addition to the multiple ways we support for handling data including Objects, Tables and Multidimensional arrays. It makes the platform more flexible and suitable for even more use cases.

130
0 12 2,337

I was trying to modify the REST.DocServer sample in the SAMPLE namespaces to use the new %Object and %Array system objects (Ensemble 2016.2 build 636) with the following changes:

/// This method returns a list of namespaces for this server

ClassMethod GetNamespaces() As %Status

{

    #dim tSC As %Status = $$$OK

    #dim tList,tNS,tFilteredList,tValue As %String

    

    #; Get the list of namespaces

    Do List^%SYS.NAMESPACE(.tList)

    Set tNS="" For  {

    

        Set tNS=$Order(tList(tNS),1,tValue) If tNS="" Quit

00
0 4 363

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.

00
0 0 203