Practical ObjectScript Coding: From JSON to Globals to SQL

While starting with Intersystems IRIS or Cache, developers often encounter three core concepts: Dynamic Objects, Globals & Relational Table. Each has its role in building scalable and maintainable solutions. In this article, we'll walk through practical code examples, highlight best practices, and show how these concepts tie together. 

1. Working with Dynamic Objects:

Dynamic objects (%DynamicObject and %DynamicArray) allow developers to manipulate JSON-like structures directly in Objectscript. They are especially useful for modern applications that need to parse, transform or generate JSON.

Example: Creating & Manipulating Dynamic Objects

// Create a Dynamic objectSet obj - {}

    // Add propertiesSet obj.name = "Vachan"Set obj.age = 25// Nested objectsSet obj.address = {"city":"Bengaluru", "zip":"560000"}
    
    // Add an ArraySet obj.skills = ["Objectscript", "SQL"]
    
    // Convert to JSON stringSet json = obj.%ToJSON()
    Write json,!
    
    // Parse JSON string back to an objectSet parser = {}.%FromJSON(json)
    Write parser.name

Best Practices:

• Always validate JSON input with %FromJSON() to catch errors.
• Use obj.%Get("property") when unsure if a property exists.
• Favor %DynamicArray for list-like structures.

2. Using Globals Effectively:

Globals are hierarchical sparse arrays stored directly in the IRIS database engine. They are extremely fast and can store virtually any structure.

Example: Storing Data in Globals

// Store student data in a globalSET^Student(1,"Name") = "Alice"SET^Student(1,"Age") = 29SET^Student(2,"Name") = "Bob"SET^Student(2,"Age") = 34// Retrieve dataWRITE^Student(1,"Name")  // outputs: Alice// Iterate over all studentsSET id=""FORSET id=$ORDER(^Student(id)) QUIT:id=""  {
    WRITE"Student ",id,": ",^Student(id,"Name")," (Age ",^Student(id,"Age"),")",!
}

Best Practices:

• Define a clear global structure before coding (avoid ad-hoc keys).
• Use globals for high-performance storage when SQL overhead is not needed.
• For application data, prefer persistent classes with globals managed under the hood.

3. Creating Relational SQL tables:

In IRIS, relational tables can be created using both SQL DDL and persistent classes.

Example: Creating a SQL Table via DDL

CREATETABLE Employee (
    IDSERIAL PRIMARY KEY,
    NameVARCHAR(50),
    Age INT,
    Department VARCHAR(50)
);

Example: Creating the same table as a Persistent Class

Class Company.Employee Extends (%Persistent) {
    Property Name As%String(MAXLEN=50);Property Age As%Integer;Property Department As%String(MAXLEN=50);
}

Once compiled, this class automatically creates an underlying global and an SQL table. You can now use both ObjectScript and SQL:

// Create and save an employeeSET emp = ##class(Company.Employee).%New()
SET emp.Name = "Charlie"SET emp.Age = 40SET emp.Department = "IT"DO emp.%Save()

// Query employees with SQL
&sql(SELECTName, Age FROM Company.Employee)
WHILE (SQLCODE=0) {
    WRITE"Employee: ",Name,", Age: ",Age,!
    FETCH NEXT
}

Best Practices:

• Prefer persistent classes for maintainable applications.
• Use SQL DDL for quick table definitions or integration with external systems.
• Always define indexes for commonly queried properties.

SUMMARY:

Whether you are parsing JSON payloads, managing high-speed lookup data, or designing relational tables, understanding when to use dynamic objects, globals, or persistent classes is key to becoming an effective ObjectScript developer.