You probably have a similar experience. The more I use Atelier the more I miss INSPECTOR that I had in Studio!
First for PROPERTIES that can inherit a variable number of Parameters beyond imagination. take %XML.Adapter as the most obvious. next: Where to find all inherited methods that I eventually want to overload? Take %Persistent as example.
Or where or how can %OnBeforeAddToSaveSet() (the correct camel case) be overloaded ?
Hello everyone, First sorry for the ignorance, but, as I am new in the InterSystem world, I came to the following doubt: Thinking about a database migration.Is it possible, in a non-traumatic way, to take an Oracle database and migrate it completely to Caché?
IRIS offers Durable %SYS Directory as a highly useful feature for working with containers.
Before inventing the wheel once more I'd like to know if a similar feature also exists for Caché / Ensemble. Official documentation is quite silent about. Though I have some names in mind that might know more about ( @Luca Ravazzolo? @Dmitry Maslennikov ? @Eduard Lebedyuk ? )
I think the forum experience is great as whole, but it could improve even more if we had somewhere to share our ideas. So that's why I'm creating a thread dedicated for that purpose. Maybe this way someone from InterSystems could catch something good?
This morning on the old Caché Google Group, someone posed the following question, which I've decided to answer here, because it's interesting!
Is there a way to iterate ClassMethod's params, and get param's names and values?
The first answer I can come up with is: it's not easy! In any method, you could try to write code like this (where methodName is the name of your method):
I found the need to merge 2 Docker images (e.g. intersystems/iris-community:2020.2.0.199.0 + my home grown NodeJS Image). I found some advice on the Web but no real convincing solution.
When I start a fresh installed IRIS or a Container I always find Interoperabiliy (aka. Ensemble) mapped to namespace USER.
Is there any utility to remove this mapping by a click ? unmapping it global by global, routine by routine, Package by Package is just a boring exercise.
To be clear: I look for a utility inside IRIS.
The external utility is obvious: Notepad (or any other text editor) - clean iris,cpf, - restart IRIS It's fast, it's efficient, but it's really hardcore.
Running WebTerminal from OpenExchange over HTTPS could be a very secure access method for remote developers. So I was asked to compare it to other access tools.
I have a Cache classes with %TimeStamp (e.g. 2016-04-18 12:29:11) and %Date (eg. 64027) properties. And I have a javascript client app, which needs full CRUD over this properties.
But in javascript date/time are defined by ISO8601 (e.g. timestamp 2016-04-18T12:29:11Z, date 2016-04-18).
Most of projects on Caché, obviously, written not only in Cache ObjectScript, and should contain sources in other languages. Such as js or css for web-projects or any others. And it would be pretty good, if I could see all of files in one project, and possible to edit all of them. How to be in this case ?
And I think it is not a good idea, to place all project's sources in one root folder. Our project contains over 3 thousands classes and routines, and it is too difficult to find anything in such folder. Is not a good for it to use Java-way, and place every package in subfolder ?
Some may think it's a strange / daft idea, but just today the Raspberry Pi folks have announced that they've now sold more than 10 million of them..and counting. That's a huge potential marketplace, and a great platform for getting people to hear about Cache and try it out. Given its focus on the education sector, another great way of getting heard about.
Starting from the point that Eclipse uses local files on the workstation, COS development can be versioned with market tools (For example GIT or Subversion).
I would like to know how the community has worked with code versioning, to create a consistent versioning model.
In a comment on this post in the Field Test - 2016.2 community Bill McCormick suggested using Atelier's "Check for Updates" option from the Help menu. Here's what I get:
By likes
