New post

#InterSystems Data Platform Blog

11

This group consists of fairly long technical posts regarding InterSystems Technology features and experience.

Every post in this group is a story of a developer or engineer who wants to share his experience related to InterSystems Data Platform with you.

Every post in this group contains either snippets of code or even ready to use projects with sources on Github or with working demos of InterSystems Technology.

Every post is reviewed by InterSystems specialists through a special reviewing procedure.

Subscribe to the group and you'll get weekly posts with essentials of experience on developing, testing, deploying, maintaining solutions that utilize InterSystems Data Platform technology: multimodel DBMS Caché,  Platform for connected applications Ensemble, analytics technology DeepSee and unstructured data management technology  - iKnow.

Yes, you can contribute to this group. If you want to share your experience, promote interesting development tool or a framework to InterSystems Developer Community in the form of a long article reviewed by InterSystems engineers - please contact me.

Evgeny Shvarov,

InterSystems Community Manager

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.

13 12
0 2.6K
Article
· May 20, 2016 12m read
Collations in Caché

Order is a necessity for everyone, but not everyone understands it in the same way
(Fausto Cercignani)

Disclaimer: This article uses Russian language and Cyrillic alphabet as examples, but is relevant for anyone who uses Caché in a non-English locale.
Please note that this article refers mostly to NLS collations, which are different than SQL collations. SQL collations (such as SQLUPPER, SQLSTRING, EXACT which means no collation, TRUNCATE, etc.) are actual functions that are explicitly applied to some values, and whose results are sometimes explicitly stored in the global subscripts. When stored in subscripts, these values would naturally follow the NLS collation in effect (“SQL and NLS Collations”).

9 7
1 2.7K