[DISCUSSION] Planning of Vstudio development for Mon - Wed, 24 - 26 Sept

[Ruslan Zasukhin]

On 24/9/07 4:35 PM, "Bart Pietercil" <bart.pietercil at gmail.com> wrote:

>> * Bart, you talk about UNLIMITED space for properties.
>>     You see need in A LOTS of properties?
>> 
> 
> status of table (internal)-->(under development,frozen for version x
> of db,in production)
> last modified by
> used by interface (we have 4 interfaces to the main db, from 2 API's
> (RB and PHP)
> ....

---------------
> I can dream up tens of things
> 
> As an example
> 
> Well one area where this could expand into and (I think) is lacking
> now is data-security.
> With properties on all levels I can make up a system where one group
> of user has MIXED rights of acces on  tables and fields (Read, Write,
> Hidden)
> And access ( read only or RW) to forms and reports)
> 
> This WILL become VERY important when databases are deployed within
> entreprises.

Well, but note, this will work in YOUR apps.

But e.g. Valentina Studio will not respect this. For Vstudio this will be
just properties of objects.


NOTE: Ask self, how RDBMS solve this tasks now?
    ANSWER IS: they just use additional, usually small tables.

So benefits are obvious!
    We get small number of tables
    We avoid joins
    We get DBMS System which KNOW that this is property of this object.


> Now once I start nagging you guys about it I am sure you will come up
> with a much better solution on the subject of data-security. But
> UNTIL you do, I can use properties (well maybe not, but there ALWAYS
> will be stuff that is linked to the way a developer works, where
> object properties will be usefull).

Right. The best security must be built-into engine.
 

> You see I can with properties do stuff like this:
> 
> if user is in group x then
> if table.field(x).ishidden<---property then set field x visible is
> false.
> 
> This is much easier then building another form and deciding what form
> to open
> 
> So in that sense it needs to be unlimited


>> * We also consider ability to access this properties as
>> 
>>         SELECT ... WHERE tblPerson. at propName = 'dfsgsdfgd'
> 
> yep, nice
>> 
>> Any more ideas?
> 
> You must be joking. I just promised myself I would not ask for more
> then 7 items per week :-)

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]