We agreed that the way to have both readonly and read-write database access was to create multiple users. Most people would know a user that was read-only so that they could not modify the db. That simply means creating multiple users in the db with varying access. The only support for that in smipyping is in the documentation.
However, we want to be sure we have a clean exception when a read-only user tries to write to the db. We need to extend the exceptions to cover this particular issue and return the proper response.
We agreed that the way to have both readonly and read-write database access was to create multiple users. Most people would know a user that was read-only so that they could not modify the db. That simply means creating multiple users in the db with varying access. The only support for that in smipyping is in the documentation.
However, we want to be sure we have a clean exception when a read-only user tries to write to the db. We need to extend the exceptions to cover this particular issue and return the proper response.