HP3000-L Archives

December 1998, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Leonard Berkowitz <[log in to unmask]>
Reply To:
Leonard Berkowitz <[log in to unmask]>
Date:
Wed, 16 Dec 1998 08:09:32 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Can someone explain this apparent anomaly and what to do about it?

An Allbase DBE attached to three TurboImage data bases resides on the HP3000. Access
to this DBE is from an HP9000. On the HP9000, the user can freely connect to the DBE
and execute queries (SELECT...) in ISQL. Now the user writes a C program to do the
same thing and comes up with an error, "User <user> does not have select authority to
<table>".

Why does the user have select authority in ISQL, but not in a local program written
and executed by that user in the same HP9000 session?

I solved the problem with a sledge-hammer: GRANT SELECT ON <table> TO PUBLIC, but
there must be a more elegant way. Yes, I can create a GRANT SELECT statement for
every table (dataset) in the DBE, and perhaps I can come up with a scheme to grant
this select to some realm that is not PUBLIC, but...

Any insights will be greatly appreciated.

========================
Leonard S. Berkowitz
mailto:[log in to unmask]
phone: (617) 972-9400 ext. 3250
fax:   (617) 923-5555

ATOM RSS1 RSS2