code, and why there are public selects on some tables?
In prior releases of Coeus, all of the search windows generated custom SQL commands. In order for this to work in Oracle 7, we had to grant public select on the tables that were referenced in query screens. As you know, this opens those tables up to uses coming in from outside the application. In Oracle 8, we are able to generate the custom SQL via stored procedures and can thereby remove the public select on the tables. It is our intention to begin migrating all of the query screens to stored procedures and remove the custom SQL from the Powerbuilder application. The custom SQL will still be constructed on the PB Client (pfc_apply event in most cases). Currently the datawindows that do the retrieve are plain SQL data source and in the pfc_apply event we set DataWindow.Table.Select attribute with the new SQL which was constructed. In the new approach for Oracle 8, the datawindow which does the retrieve will have a stored procedure as the data source. This stored procedure takes one arg
Related Questions
- For further information on your responsibilities and, what you need to do, please consult the Code of Practice Rights of Access: services to the public, public authority functions, private clubs and premises (new window). Can I appeal against a decision on my planning application?
- What is the four letter department code for the School of Public Policy?
- code, and why there are public selects on some tables?
