This typically happens when you have some corruption of the Extent information for your namespace.  You'll want to delete the nodes for digi.packet in ^oddEXT and ^rINDEXEXT (in the "G" and "U" nodes, I believe).  You can try running ##class(%ExtentMgr.Util).DeleteExtentDefinition("digi.packet") but I'm not sure if that will get it all the way done.

The easiest thing to do might be to export all your classes and import them into a fresh namespace (as you noted this works in many other places).  If you want more step-by-step guidance or any root cause analysis, I recommend contacting InterSystems Support (

Joe Gazillo!  Good to hear from you!

I think that code should work back to 2016.2.  Basically after the change to our JSON objects.  To work on 2016.1 you'd have to change %Push() to $push().  Earlier versions, you'd have to something with the %ZEN.Auxiliary.jsonProvider to get that to work.

Can you not edit answers that are "accepted"?  Because my code is wrong and  needs updating.

Class Def

Class User.JSONify Extends %Persistent


Property JSONData as list of %String;


ClassMethod MakeJSONArray(list) as %DynamicArray [sqlname="MakeJSONArray", sqlproc]


                q:(('$listvalid(list))|| (list="")) ""

                set jsonarray=[]

                for i=1:1:$LL(list)


                                d jsonarray.%Push($ListGet(list,i))


                q jsonarray




Data Population

USER>s obj=##class(User.JSONify).%New()


USER>s json="{""Name"":""Kyle""}"


USER>w obj.JSONData.Insert(json)


USER>s json="{""Name"":""Evgeny""}"


USER>w obj.JSONData.Insert(json)   


USER>w obj.%Save()




3.            select JSONData,MakeJSONArray(JSONData) from JSONify


JSONData             Expression_2

$lb("{""Name"":""Kyle""}","{""Name"":""Evgeny""}")           17@%Library.DynamicArray


1 Rows(s) Affected

statement prepare time(s)/globals/lines/disk: 0.0507s/37476/174342/0ms

          execute time(s)/globals/lines/disk: 0.0003s/2/598/0ms


Extra Proof
USER>s sql="select JSONData,MakeJSONArray(JSONData) from JSONify"


USER>s rs=##class(%SQL.Statement).%ExecDirect(,sql)


USER>w rs.%Next()


USER>s json=rs.%GetData(2)


USER>w json


USER>w json.%Get(0)


USER>w json.%Get(1)


Not 100% on this design, but getting it to work isn’t bad.  You’ll need extra error checking crap in any REAL code, obviously (for instance, I do ZERO checking to see if what is in the list is valid JSON).



Edit: Adding parens around list="" as is proper when writing ObjectScript code.  Due to ObjectScript's left-to-right evaluation, it is important to always wrap your conditions in parens or risk getting some unexpected results!!!

AVG exists in 2015.1.  If you want the median you might have to calculate that yourself within a function.  Do you need an SQL-only solution?

Sorry, perhaps I need to give a little more background than exactly none :-)

The way Atelier connects to Caché (eq. Ensemble, HealthShare, IRIS) is via a webserver.  Atelier connects to the webserver and the webserver connects to Caché.  What you need to do is set up the webserver to allow HTTPS connections.  To do this, you could use the Private Apache that we ship with Caché (eq. ...), or you could install a full version of Apache or IIS to do this.  Alternatively, you could set up a webserver local to your machine. 

Honestly, you might be better off opening a WRC case ( or and one of us would be happy to help you in all the gory details.  There are lots of questions to be asked here such as what attack vectors are you protecting against and where your server, webserver, and Atelier are all installed.. 

Did you enable HTTPS on your webserver?  If so, that typically means a new port (default: 443), which you would need to add to your connection.  If not, do you know how to enable HTTPS on your webserver?

The answer to your question is 'almost never'.  If you run TuneTable on your class/table then you will be required to do a purge so the optimizer can pick up the changes.  Aside from that, the Caché engine should handle all purges automatically.  If you change a class and compile it, that compilation should trigger a purge of the appropriate cached queries.  If you are finding that it does not, then please contact the WRC so we can get this fixed.

If ever you are looking for generalized information, you can always look at as well as the documentation (   There's a lot of good videos there that you can use to help get going.  If you have any specific questions there are plenty of us who would be happy to answer them.

Hey Laura!

OK so if Frozen Query Plans was your problem (and it's a good hypothesis), then unfreezing them all gets you back to the old behavior (you'll need to recompile and purge cached queries).  There were some problems with the 'old' dynamic SQL classes, but I think those were solved, so you shouldn't have any problems going forward.  So let's talk about this a bit.

What are Frozen Query Plans?
If you've ever upgraded Caché and had a critical query degrade in performance, you'll agree this technology is pretty cool.  What it does, is to lock down your query execution plan during upgrades (or it can be user [you're the user] initiated). 

Benefits: No bad surprises during upgrades
Drawback: No benefits from core improvements to SQL engine

Is it a problem to Unfreeze all plans?

No!  Of course not.  You will absorb some risk, but if you usually don't have problems then you will continue to not usually have problems.  If you unfreeze all plans you'll need to compile your application and/or purge cached queries.  To do this you can execute the following in your application namespace:

w $SYSTEM.SQL.FreezePlans(0,1,,.err)
d $SYSETM.SQL.Purge()

You can obviously look this up in the docs for more information.  If you have embedded SQL queries those would need to be recompiled.

Dynamic SQL Implementation
We (InterSystems) recommend using %SQL.Statement in lieu of %ResultSet for dynamic SQL.  When you ask if you should change, the answer is 'yes'.  However, this only fixes your problem because when you use %SQL.Statement it ends up being a slightly different query according to our Frozen Query Plan implementation.  It fixes your problem, but not the root of the problem.  %SQL.Statement is also fine to use for 'older' code.  Of course, if you don't want to change your code ("if it ain't broke"), that's understandable.

SELECT * queries

Running a SELECT * query is a bit of an edge case.  It is frequently better to list out your fields so your are only showing your users the data they are interested in.  Indeed, you can only run into this problem if it is a SELECT * query.  In general, list out your fields.


So that's that.  If you have any further questions, feel free to let me know :-)