New answers tagged


Try this. You don't need a different table, although if you have one it could help.


AIUI, your wish is to shorten the RETURNS clause of the function. Not sure if you want to establish a dependency on the row type of the table at the same time, but that would make sense here, too. The form RETURNS SETOFrettype relies on the used type to be stored in the system catalogs. The manual: The return type can be a base, composite, or domain ...


This seems to be an on-going issue Views are messy to handle with Dynamic SQL Earliest Bug was Cannot create VIEWs in prepared statements from 11 years ago. There was a patch put in to address it. Another bug report, Prepared-Statement fails when MySQL-Server under load, states that error 1615 is not a bug when the underlying tables are busy. (Really ?) ...


SELECT * FROM tbl a WHERE deleted IS NULL AND EXISTS ( SELECT * FROM tbl WHERE id = a.parent_id AND deleted IS NULL ); See if that works, then turn it into a VIEW.


As I already said, ORA-03113 is a generic error. When that error occurs, the server process serving your session died unexpectedly because of some other error in the background. These errors are displayed in the database alert log. In your case: ORA-07445: [kkqtutlSetViewCols()+250] [ACCESS_VIOLATION] [ADDR:0x8] [PC:0x3DC175C] [UNABLE_TO_READ] [] You ...


Do you need to grant permissions to every object built underneath the views? Or just the view itself? Or either one? Permissions need to be granted to the person executing the query for every object referenced by the view. Except if they are owned by the view owner. In that eventuality Ownership Chains come into play. When an object is accessed ...


It's the owner of the view that needs permissions to the underlying table, not the person querying the view. If you're getting a permission denied message when querying the view, it might be because the view owner doesn't have the appropriate permission to one of the underlying tables.

Top 50 recent answers are included