Is it possible to map a package as read only?

Question

Question

Jonas Zanon · Dec 12, 2019

Hello guys,

I know it is possible to mount the source database as read only and map the package in the target namespace. But I would like to make the mapping read only so that the package would be "read only" only in the target namespace.

This would avoid someone to forget to set the database read only again if a modification in the package is needed.

Thanks in advance.

Jonas Zanon

Discussion (3)1

Log in or sign up to continue

Peter Steiwer · Dec 12, 2019

Would this be for a Development System or a Production System?

If it is a Development System you could consider using source control hooks to basically prevent people from modifying the class unless they first check out the file. If they attempt to modify it without first checking it out, they will get a message saying they need to first check out the file. If they do not have permission to do so, they will not be able to. If they do have permission to, using source control will allow you to revert any changes that end up causing issues.

If it is a Production System, you can consider using deployed mode. See documentation here. The documentation says: "You can open the class definition in Atelier, but it is read-only." (This is true for Studio also).

As you mention, making the Database Read Only is also an option.

0 0

score 0 · Answer 1 · 2019-12-12T09:31:17-05:00

Here's how.

1. Create a hardlink to the original database in a new empty folder.

2. Add this new database.

3. Mount new database as readonly.

4. Map package from this new database.

This way you can access code for RW (in original namespace/database) and RO (in hardlink database).

Just tried this setup and it worked.

score 0 · Answer 2 · 2019-12-12T10:18:04-05:00

Jonas Zanon · Dec 12, 2019

Thanks Edward!

That would do it. I'll try and let you know.

0 0