Re: Can these constraint be implemented in an RDBMS ?

From: mountain man <hobbit_at_southern_seaweed.com.op>
Date: Wed, 03 Mar 2004 07:54:39 GMT
Message-ID: <3bg1c.84668$Wa.5455_at_news-server.bigpond.net.au>


"ben brugman" <ben_at_niethier.nl> wrote in message news:404497db$0$3681$4d4ebb8e_at_read.news.nl.uu.net...

...[trim]...

> Do you have a solutions for this type of problem within your 'RDBMS' ?
> Is access control part of a 'RDBMS' ?

Everything that you have written in this thread can be implemented on SQL Server for sure. I would reckon Oracle would also have zero problems.

Contraints are able to be written in the native RDBMS language (eg: TSQL for SQL Server) and bound to the database tables. All data entry routines are able to be written as stored procedures, as are all report writing requirements.

At some stage you need to deal with someone skilled as a DBA or in coding TSQL (for example.

Access control is handled by the user security system that is part of all RDBMS software products. Integration of that security system to your organisation is simply a mapping of people to organisational work-groups, and the mapping of those workgroups  to the applications available to the work-group.

The classic example of the above is a Menu system that is organisational sensitive.

Good luck with it!

Pete Brown
Falls Creek
Oz Received on Wed Mar 03 2004 - 08:54:39 CET

Original text of this message