I can think of the following reasons:
- If the table structure is changed ( a field is added ), the program will have to be modified
- Program might retrieve the columns which it might not use, leading on I/O over head.
Code: Select all
SELECT ... ... ...
<list of column names>
INTO <list of host variables>
... ... ...
Code: Select all
SELECT *
This is very late to acknowledge the reply but I was not aware about that we can RACF secure some columns out of many. That's a news. But why would someone create a column and then don't allow the access to it?MartinPacker wrote:SELECT * when all you wanted was columns in an index prevents index-only access. And I'm sure there are other access path no-nos.
It also occurs to me that if column data is (eg RACF) protected then the request will fail, whether you wanted columns you don't have access to or not.
Of course an unqualified row selection is equally problematic, which is what I mistakenly originally thought the question was about. :-)
Thanks!nicc wrote:You don't 'not allow access' - you create a column and restrict access to it i.e. if you have a need to know that data and have the access then you can select it. If you don't have the authority then you cannot.
You need to be a member in order to post a reply
Not a member? register to join our community
Members can start their own topics & subscribe to topics
It’s free and only takes a minute