Re: Ownership of data[bases] (was: SQL Syntax)

["David Gibbs" <david@xxxxxxxxxxxx>]

John wrote:
> Those days are over.  It's the user's data base.  They should have
> direct access to it, and you cannot predict their ad hoc uses
> from a myriad of interfaces.  The Joins, Views should be designed
> just as much for the End User's need as it is for OUR program's
> needs.

Then I wrote:
> The software package his department is using does *NOT* allow user access
to
> the database directly.  Not even for READ access.  The software provider
has
> secured the database in a way that you need a userid & password to access
> the data, and they will NOT give their customers the necessary user id.

And then Joe wrote (in the original thread):

> And I still disagree.  While the data may be the user's, the database is
> MINE and always will be.  I don't want the user to EVER see how I have
> stored my data.  It's my job to store it, manipulate it, and get it back
to
> the user.  That way I can guarantee integrity.  Without that, all the user
> gets is data, not information, and there is a HUGE difference.

Hmmm ... an interesting POV.  Not one I disagree with.

Question related to that ... would you advocate restricting ACCESS to the
data (in it's raw form)?  What about access to "Logical" data (defined sets
of data with logical data appropriately joined)?

david