AllAccepted answers
David Underhill · Aug 18

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

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

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 · Feb 5, 2024

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 · May 6, 2022

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

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

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