Exclude globals from mapping

Question

Question

john smith · Aug 13

Hi

I've more than 100 classes that are packed like CRD.Health.MyClass so I've defined the global mapping as CRD*, but now I would like to map some of the classes (CRD.Health.SomeClass) to different database so how can I exclude it from my current mapping to be in the new one because if I map it in the new database it will still conflict with the old mapping?

Thanks

Product version: Ensemble 2018.1

Discussion (2)2

Log in or sign up to continue

score 0 · Answer 1 · 2024-08-13T05:42:59-04:00

The DB mappings go from least to most specific, so you could have a set such as

GLOBAL* - GlobalsDB

GLOBAL.PKG* - PackageDB

GLOBAL.PKG.Excluded* - GlobalsDB

There is a bit of management overhead in this as you start getting more specific, but this should work

score 0 · Answer 2 · 2024-08-14T02:09:03-04:00

Yep I know that but that doesn't help in my case, because I need the most specific in a separate database and as i mentioned I have more that 100 classes (globals) so yes I can map and specify my Global.pkg.MyClassGlobal in the new database but I already mapped Global.pkg* in the old because I have many classes in Global.pkg and I don't want to map one by one in my pkg and exclude Global.pkg.MyClassGlobal ?
So I guess I'll have to go pkg then classes that starts with eg. A, B ...etc (eg. Global.pkg.M*) in the pkg, exclude Global.pkg.MyClassGlobal and map it by itself in the new DB instead.
All good thanks Chris