Also available on OpenExchange

Hi Felipe!

Are you able to edit ANY files with VSCode? With ObjectScript files, it should be the same.

Just to make sure: 

1. - check out your ObjectScript files from the repository to a local file folder.

2. Open this folder in VSCode.

3. Setup the connection in VSCode to an InterSystems server and namespace you want your files to be compiled.

4. Code it!

There are also other steps of commit/push/test/patch/deploy - but it is another story.

And you can check connection and compilation logs in Output/cos window, see the gif above.

Hi Felipe!

As @David Reche mentioned you can get it from the Command Palette menu and as you can see Command +F7 hotkey can be used for import+Compile.

I also like the option:

cos.Autocompile=true;

which gives you compilation on every Save (Command + S) and which you can setup in workspace settings of VSCode.

Also, make sure that you connect to a right server and right namespace. See the following gif which illustrates how it works:

What is great about InterSystems objects is that you exactly know what's going on with your data. 

You can look into the generated code for classes with Cache Storage and see where and when class writes the data into ^OBJ.DSTIME when the class has 

Parameter DSTIME As STRING [ Constraint = ",AUTO,MANUAL", Flags = ENUM ] = "AUTO";

So, there is no magic here:  DSTIME=AUTO parameter introduces "sets" into ^OBJ.DSTIME global in the places where records are being updated or created.

It doesn't work for non-standard SQL storage because DSTIME Parameter simply doesn't know about insert/update/delete procedures anything.

In your case you can forget about DSTIME and place this sets in Global (or inserts into some Record.ChangeHistory class) in the places, where your data is being inserted/updated/deleted.

Hi Eric!

Thanks for your interest!

Conctacted you directly.

Hi Yaniv!

As @Chris Thompson mentioned you can use DSTIME for automatic records changes tracking which will be stored in a special global. But I doubt if it works for classes with non-standard storage schema just by adding DSTIME=auto;

How do you add/update records in your application? You need to introduce special calls in your "create/update" procedures to track changes. DSTIME=auto; does exactly same adding "tracking" logic in SQL and Object requests for class changes. Maybe you can use some calls with DSTIME=manual; mode.

@Alexander Koblov  do you know if it is possible to use DSTIME somehow in this case?

Another approach which may work in your case is to use AUDIT to track the changes users made to DB and then analyze this data, e.g. like here. But I never did it for non-standard storage schema.

Converted to an answer

Converted to an answer.

Converted this to an answer

Hi, Robert!

Just want let you know that we finally introduced one (ONE!) button for ObjectScript highlighting.  E.g. your code:

set %ref="obj."_prop,key="" for  set key=$order(@%ref@(key),1,val) quit:key=""  write key,?5,val,!

Can be highlighted like this:

Why "-0"? 

Just "*" will be enough:

set name=$E(name,3,*)