go to post Evgeny Shvarov · Dec 3, 2018 It's the 3rd day! Join InterSystems ObjectScript competition! (it needs you to be logged in first).We'll introduce some incentive from InterSystems soon ;)
go to post Evgeny Shvarov · Nov 29, 2018 That's easy:1. Register on Open Exchange - in your case just sign in with same credentials as on DC.2. In your personal page submit a new app which is the set of Name, Description, Github, License and Product link.3. Submit for Approval.That's it.Once approved start to receive the traffic for your application via Open Exchange.There is a dedicated post on how to submit the application
go to post Evgeny Shvarov · Nov 28, 2018 Hi Ivan!Thanks for sharing the project!Do you want to also to list it on Open Exchange?
go to post Evgeny Shvarov · Nov 27, 2018 Hi Felipe!Recorded the short "Coding video" to illustrate how it code and compile ObjecScript in VSCode.
go to post Evgeny Shvarov · Nov 27, 2018 As it was announced on Global Summit it should happen in November. We have at least one more week of November. So, stay tuned )
go to post Evgeny Shvarov · Nov 25, 2018 Also available on OpenExchangeThe new version has independent mobile UI for DeepSee dashboards.
go to post Evgeny Shvarov · Nov 25, 2018 To join Global Masters leave a comment to the post and we'll send the invite.
go to post Evgeny Shvarov · Nov 19, 2018 The title looks "scary" )Dmitry, does your approach need Caché Studio only? Could it be used for Eclipse or Visual Studio Code?
go to post Evgeny Shvarov · Nov 16, 2018 Thanks, Robert!I realized now that DR site should be in another cloud and on a distance because of the purpose.DR is being implemented as ASYNC Mirror in InterSystems and I think the network performance/bandwidth is the key.All you mentioned here is fair enough, thanks.And what I realize in the end that network bandwidth requirements totally depends on the transactions load of the PRIMARY.The hardware requirements of DR site is an easier thing - DR site can have the same configuration as PRIMARY.
go to post Evgeny Shvarov · Nov 16, 2018 Thanks, Ed! So that means if you have enough bandwidth and not an awful lag you can place your async mirror even in another cloud.Do we have any minimum bandwidth and lag requirements?Can we measure it somehow between two servers before starting the mirroring?
go to post Evgeny Shvarov · Nov 14, 2018 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.
go to post Evgeny Shvarov · Nov 13, 2018 And you can check connection and compilation logs in Output/cos window, see the gif above.
go to post Evgeny Shvarov · Nov 13, 2018 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:
go to post Evgeny Shvarov · Nov 12, 2018 Hi Jan!The support of Hibernate 5.2 or 5.3 is stated in IRIS 2018.2 release notes. Hope it solves the issue.
go to post Evgeny Shvarov · Nov 12, 2018 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.
