All
Accepted answers
David Underhill · Mar 24 go to post

Just realised this is an old(ish) post but it has had a recent response so I'll still add the below FWIW...

This is nice an simple but be aware it doesn't handle commas, or other potentially problematic characters, in a string value.

CSV requires that any value containing quotes or the delimiter (comma) should be quoted, anything that reads in CSV should handle this.

Given an example "one,2,three,4" your example works but """one,"",2,three,4"  will not, it will create a list with 5 parts.

set line = """one,"",2,three,4"
set fields = $ListFromString(line, ",")
for n = 1:1:$listlength(fields) w !,$list(fields,n)

"one
"
2
three
4

The %SQL.Util.Procedures class has some useful CSV methods or take a look at CSVGEN.
 

David Underhill · Sep 26, 2025 go to post

Just as an example, an alternative with $piece.
An issue would be if both startStr and stopStr are the same value which $find does solve.

set values=""
for n=2:1:$length(text,startStr) {
    set check=$piece(text,startStr,n)
    if check[stopStr set values=values_" "_$piece(check,stopStr)
return $piece(values," ",2,*)
David Underhill · Aug 27, 2025 go to post

Great overview, I have had plenty of discussions with IT departments who don't understand that Linux, and Windows, will use available resources, especially for IO, and it is only an issue if it is persistent or unusual, and obviously if there are performance/stability issues.
Being able to provide metrics over time and proving it is "normal" usually helps.

David Underhill · Aug 21, 2025 go to post

This looks so much easier than when I had to do it and is very welcome. 

At the time I moved it to a personal email so I didn't have to do it again changing companies. 

This means it should actually be possible to keep it linked to wherever you are working.

David Underhill · Aug 18, 2025 go to post

I appreciate the comments, some things to think about.

If you have planned tables and data properly uniqueness should not be an issue and it looks like the performance consideration is unlikely to be a problem in most cases.
Being able to check the raw data easily with a standard global naming is, for me at least,  a benefit of not using the hashed names.

However, knowing these reasons is very helpful in planning and identifying those edge cases.

Is there anything else I have missed that would make this more of an issue?

David Underhill · Aug 15, 2025 go to post

Without someone providing an accepted linter you won't get everyone to agree on case etc...

My own preferences do not all match the above but if we had a defined ruleset that was easily managed and enforceable in the IDE then fine with me.

However, I think we should all be able to agree that moving away from shortened commands and names benefits code maintenance and readability plus aligns better with other languages, especially if we use classes, braces, and other "modern" objectscript styles.  Yes I know that I am showing my age, but note I avoided mentioning the "M" word 😂

David Underhill · Aug 15, 2025 go to post

Nice documentation.

Some niceties to add that I encountered, all available in the documentation link Iryna provided.

- The generated global names are often not very intuitive, you can set these yourself in the CREATE TABLE using 

%CLASSPARAMETER USEEXTENTSET = 0,
%CLASSPARAMETER DEFAULTGLOBAL = '^Packagename.Tablename';

- For concurrency checks similar to PostgreSQL you can add a version property.

CREATE TABLE ...
(
...
xmin INT,
...
)
%CLASSPARAMETER VERSIONPROPERTY = 'xmin'
David Underhill · Apr 29, 2025 go to post

If you don't use Inter Job Communication devices then set IJCBUFF and IJCNUM to zero.

You can also zero NLSTAB if you don't modify collations.

I would also turn off NETJOB if not running ECP.

David Underhill · Feb 5, 2024 go to post

Very useful.

I tend to avoid post conditionals nowadays as I long ago realised, as with your other examples, readability was far more important.

Only one I do not personally do is the Command Arguments example, I'm old and set in my ways and like using the comma 😁

Another possible mention might be "goto".

Oh, and your note on functions not being case-sensitive is only for system (intrinsic) functions.

I think the message overall is we no longer have the same memory and screen limitations and so spaced out, readable, and maintainable code is far more important than the old compacted method of writing mumps/objectscript. 

David Underhill · Aug 30, 2022 go to post

Thanks for the reply.

If a user needs to be able to monitor and operate a Production would they not still need access to that data base?  Also, that table is granted via %ENSROLE_OPERATOR which such a user will need?

David Underhill · May 6, 2022 go to post

Thanks for the explanation, I assumed it worked something like that.

Do you agree with that approach though or would you prefer something more like Robert's description?

In my mind you don't create a database based on a specific file so the DAT should be swappable and retain the database settings, other database settings work that way.

David Underhill · May 5, 2022 go to post

Hi, that was my understanding but I have seen resource issues caused by moving CACHE.DAT in the past and recently had an odd issue on IRIS then did the below to test it.

I just copied the IRIS.DAT from the USER database folder, which has the %DB_USER resource, to another database folder which had %DB_%DEFAULT and afterwards the other database had %DB_USER instead of %DB_%DEFAULT and so it seems the Resource does move with the DAT file.
The copy was done manually with windows file copies while IRIS was down and no config changes made.

This is all viewing the database resource via the portal in  System > Configuration > Local Databases

David Underhill · Apr 11, 2022 go to post

That removes all " characters, while these are indeed doublequote's, someone could also mean "" where there are double quotes, as in quotes inside a quoted string (str="this is a quote"".")

For that

$translate(str,"""""","""")

or I find it more readable to use the ASCII value so to remove

$translate(str,$c(34.34),"")

or to replace with a single "

$replace(str,$c(34,34),$c(34))
David Underhill · Mar 29, 2022 go to post

Good point, I guess it depends on the variables scope at that stack level, I generally just run it twice.

Either way, as you say, it is useful to know to do this to ensure "leftovers" don't interfere with later commands.

David Underhill · Mar 10, 2022 go to post

Not 100% sure of the requirement but if you write the output from the Cache code as if it was to the terminal then you can redirect the output to a file by appending >output.file but I don't think cterm is the way to do that as cterm will trap all the output itself, you would need to use csession for that.

You could just write to a file in your Cache code or run an external command/script from inside the Cache code?