Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

better support across upgrades #51

Open
canzanos opened this issue Nov 15, 2019 · 0 comments
Open

better support across upgrades #51

canzanos opened this issue Nov 15, 2019 · 0 comments

Comments

@canzanos
Copy link

The code works fine. The one issue I have is the name of the objects. According to Intersystems documentation

Custom Items in CACHESYS
You can create items in the CACHESYS database. When you install a Caché upgrade, this database is upgraded. During this upgrade, some items are deleted unless they follow the naming conventions for custom items.
To add code or data to this database so that your items are not overwritten, do one of the following:
Go to the %SYS namespace and create the item. For this namespace, the default routine database and default global database are both CACHESYS. Use the following naming conventions to prevent your items from being affected by the upgrade installation:
Classes: start the package with Z or z
Routines: start the name with Z, z, %Z, or %z
Globals: start the name with ^Z, ^z, ^%Z, or ^%z

I had previously installed your code and it was working fine. I upgraded Cache/Healthshare and as part of the upgrade all of %SourceControl was removed.

Could this code either

  1. be named %ZSourceControl.*
    or
  2. be formally included in a Cache/Healthshare kit

so that I do not have to re-apply the code after an upgrade?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant