#Namespace

We want to isolate the storage of our CCDAs from our HL7 V2 data, but keep them under the same namespace. From my understanding, I should create a new database then store those classes related to CCDAs in that database. Is this the correct approach?

Hi community,

We have a developed a new version of a production, all the code is new and has changed BP. This application load information for some brands and stored in database.

The customer wants to implement the changes only for some brands because he wants to check for small brands before to implement for all brands.

My proposal is create a new namespace, with the new code, and disabled all load of brands except the brand that he wants to check.

I'm wondering what is the best way to clone the namespace.

Hi everyone.

Is there a sensible approach to having a lookup table in Namespace A, and then accessing this from Namespaces B, C, D (etc)?

I'm trying to avoid creating a Global mapping of the lookup table global (^Ens.LookupTable) as I fear that it would then link all other lookups in that global and lead to some unexpected behaviour, but would be open to trying something in this realm if it's the best option.

Hi All,

We have a licensed version of Ensemble but for now, we use only the DB capabilities of Cache. As we create a custom Namespace, for e.g "Test", a new Ensemble Namespace is automically created by the system --"TestENS".

Is there any way where we can identify the system created ENS namespaces ?

I have multiple namespaces in a Cache environment say NS1 & NS2. I want to add some restriction so that a routine running in the NS1 should not access any resource(global/routine) belongs to namespace NS2.

The above restriction need for few of the clients only, so we do not want to write any custom logic in code.

We are looking for some solution provided by Cache where we can restrict the namespace access.

Can somebody please help me on this.

Have enabled LDAP for our numerous , Ensemble, IRIS and cache instances with many namespaces. All is working fine and the ldap logins work.

But have noticed that the first instance that the user logs into the namespace is assigned to that user, but when that user than logs into another instance the default namespace from the first login is still there and doesn't update to the new namespace.

So this doesn't effect the ldap login but is now effecting the terminal logins where the user is now getting access denied.

Hi Community!

What's the limit for Namespaces and Databases for one InterSystems IRIS installation?

Yes, I checked with documentation but cannot find it at once.

Hi All.

Had an empty Ensemble namespace (interoperability enabled) which the customer had requested renaming before beginning development, so was wondering about best practice to achieve this.

I just realized that for the latest version of IRIS for Health 2023.3 the method InstallFoundation from HS.HC.Util.Installer has just disappear. I checked the official documentation (here) but I can't find any reference to it like in previous versions (here).

Currently we are exploring how we can allocate additional disk space to our current environment as we have seen a significant increase in growth of our Database files. Currently we have 3 namespaces, all with 1 IRIS.dat each that contains both the Global and Routines.

Since we have started down the route of everything within a single IRIS.dat file for each namespace, is it logical as we see growth to be able to split the current IRIS.dat for each namespace into a separate IRIS.dat for global and a IRIS.dat with for routines for each namespace in a Mirror environment?

I am trying to locate a method that would allow me to differentiate between InterSystems preinstalled/system namespaces and "our own" namespaces. I am interested both in Cache and Iris answers if they are different. Yes, I can list what to disregard, like if not HSLIB or if not DOCBOOK but hoping for a more universal and elegant answer.

Hi all.

I hope you can help me.

I've renamed a namespace and its databases names.

• Old Namespace: LABORATORIO
• New namespace: SRV-LABORATORIO

The rename of all has worked fine. When I've tried to access to the portal, it is no available, displaying the message "Tha namespace SRV-LABORATORIO does not support productions"

So, I've run the following command in terminal

Hi

I'm having a tidy up of code across my multiple namespaces, and have moved the common code to a new database called DEVTOOLS.

Currently, I'm copying code and updating code into new namespaces.

How might I make code from namespace available to others?

Cheers

Andy

Hi all,

I noticed today that when adding a namespace (localhost) to the Workplace in VS Code, it is being created as read-only.

I haven’t encountered this issue before - previously, I was able to add the namespace with full access and could edit files without any problems. The settings appear to be the same as before.