Re: Can these constraint be implemented in an RDBMS ?

I am sorry but I misunderstood you totally. To explain what I meant :
You wrote :
"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."

I write
"Everything that I have written in this thread can be implemented in a Assembler language. That includes the complete RDBMS code"

Although this is true, pointing towards the capabilities of what technically can be done, is something different than explaining what a system contains.

A mountain of bricks is not a castle, one can construct a castle from it but that is not the same.

The RDBMSses I know, do not have "content based security". On the other subject "Menu's", I do not know what you mean by menu's; a procedure (T-SQL) is not designed to interact with a user and therefore not suetable to work with menu's, yes you can generete lists to use in menu's but you can not build a menu system with it. (That is what I mean by menu's.).

In General, using T-SQL compared with using a high end language (and developing environment) is severly limited in possibilities. In Assembler you can construct anything as wel, but that does not mean that it is 'an application', 'a rdbms' etc, and it is not a preverent way to build an application.

ben brugman

>
>
> The RDBMS is delivered with native utilities which include SQL.
> In SQL server this is called TSQL. Using TSQL, if you know
> what you are doing, you can construct literally anything that
> you are capable of imagining. If you do not know SQL, then
> find someone who does, and run this passed them.
>
>
> > > > > The classic example of the above is a Menu system that
> > > > > is organisational sensitive.
> > >
> > > > Menu systems are not part of RDBMSsen.
> > >
> > >
> > > How did you arrive at this conclusion?
> >
> > Could be that I understand Menu system different from you,
> > but I associate a menu with userinteraction (for any menu), and
> > user interaction is not something that I associate with RDMBSses.
> >
> > (Of course for managing an RDBMS menu's can be used, but managing
> > an RDBMS is not the RDBMS itself.)
> >
> > But again maybe I missed what you mean by a 'Menu system'.
>
> A menu system can be as simple as a common stored procedure
> (written in TSQL or SQL) by which each user account is parsed
> at the gate to the system and in return presented with an appropriate
> selection of menu items.
>
> Normally the menu system is mapped to the organisational workgroups
> (eg: sales, accounts, customer service, EIS, etc).
>
> A menu system is easily constructed using TSQL. A great deal of
> functionality (indeed an unlimited amount) can be achieved using only
> the native utilities within the RDBMS, independent of your development
> language or platform.
>
> Good luck with it!
>
>
>
>
>
>
>
>
>
>
>
Received on Sun Mar 07 2004 - 14:15:23 CET