-
Gerrat Rickert
- PowerBuilder
- Monday, 25 May 2026 06:27 PM UTC
When logged in as the schema owner, for tables with a primary key, one can open an iSQL session, type:
> select * from some_table
and then proceed to edit values in some_table directly.
In terms of auditing, logging in as the schema owner isn't ideal, as there is no way to tell who actually made changes if everyone just logs in as the schema owner.
This also isn't great security-wise, as one has to change that schema password if one wanted to remove someone with access.
The answer to this is to log in as a proxy user - the database acts as if you were the owner of the schema, but still "knows" who you are. After enabling the appropriate permissions, in order to connect to "a_schema" by proxying "a_user", one would just use:
a_user[a_schema] for the Login ID, and enter a_user's password.
Now, queries don't have to be prefixed with the schema, special permissions don't have to be granted to a_user - everything just happens as if a_user is actually logged in as my_schema.
However, Powerbuilder doesn't treat this proxied user as "my_schema".
It won't allow updates from the iSQL results grid.
(one could prefix all tables with the schema owner, and that would allow updates, but that is very inconvenient vs just logging in as the schema itself).
The Powerbuilder Catalog Table Owner is set to "my_schema", and I've tried setting the current_schema, but that doesn't make a difference.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.