Results 1 to 4 of 4
  1. #1
    Join Date
    Dec 2003
    Posts
    1,074

    Unanswered: REFERENCES privilege on a VIEW

    I noticed that one of our developers added a REFERENCES privilege on a VIEW by accident. What would be the reason to add this type of PRIVILEGE on purpose?

    -Chuck

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    It is required when PK/FK exists across two schemas.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Dec 2003
    Posts
    1,074
    Right, but why is it allowed on a VIEW?

    Code:
    SQL> create table a_table (field number);
    
    Table created.
    
    SQL> create view a_view as
      2  select * from a_table;
    
    View created.
    
    SQL> grant references on a_view to public;
    
    Grant succeeded.
    v. 10.1.0.3.0
    -Chuck

  4. #4
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171
    Provided Answers: 1
    You can create constraints on views too, for use by the optimizer. They are not enforced however.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •