The delimiter should not matter as long as you handle quoting fields that contain the delimiter or quotes (making sure to double-quote inside a quoted field). 

It sounds like a faff but is not actually that difficult to code, for either output or input, and is a pretty standard way to handle CSV.  Also the class %SQL.Util.Procedures can be useful or there are some examples in Open Exchange.

I would also add making sure your migration is either restartable, from a point of failure, or can catch up on failed entries, after tweaking either the code or data.  You don't want to have to run the whole thing again and which  negation method you opt for depends on whether the data must be loaded in order or not.

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.
 

🥳

Delve more into AI and it's application both in DEVOPS and application functionality.

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,*)

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.

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.

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 😂

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'

Definitely someone worth celebrating.

Well done John.

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.

DC Search by a single or range of versions applicable: Search by version | InterSystems Idea

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. 

Hi,  best thing would be to not use the built-in web server (PWS) and set-up your own Web Gateway in IIS or Apache.

These are links to some of the relevant documentation

Web Servers for Microsoft Windows | CSP Gateway Configuration Guide | Caché & Ensemble 2018.1.4 – 2018.1.8 (intersystems.com)

Web Gateway | InterSystems IRIS Data Platform 2023.3
 

Pipes are also a good way to interact with an OS command or external program

Pipes | InterSystems IRIS Data Platform 2023.3

%SYSTEM.OBJ has various compile methods, you can compile individual classes, whole packages, whole namespaces, and so on.

https://docs.intersystems.com/iris20201/csp/documatic/%25CSP.Documatic…

You can also use them via $SYSTEM.OBJ... instead of ##class(%SYSTEM.OBJ)...

It's good to hear this is going to be added.  In the meantime we found using explicit ftps got around it but that may depend on how the ftps server is configured.

For explicit ftps I got a very helpful answer in a previous post

Explicit FTPS in Cache | InterSystems Developer Community | Data Import and