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

Thorsten Hohage thohage at objectmanufactur.com
Mon Sep 24 16:05:30 CDT 2007


Trying to give some answers, before reading this whole thread!

On 2007-09-24, at 14:45, Ruslan Zasukhin wrote:

> But as you and we understand now, we have start much more DEEP  
> feature for
> Valentina 3.5.
>
> We are going implement new OR feature of Valentina Database Model:
>         "Properties of Database Objects"
>   aka   "Static Variables of Classes"
>
>
> QUESTION IS:
>
> * Bart, or others. Do you see real-life examples when PROPERTY of
>     Database/Table/Column/Link  can be useful?

Yes several!

I.e. storing class information for the application on the "client"- 
side. For now I'm going to write several XML-Files for mapping and  
much more needed informations, configurations and actions.

Thinking of properties I can imagine a "special" version of my  
frameworks, where no XML-file is needed, but everything stored in the  
properties.


I think this is a feature where we need some time to develop ideas  
how and when to use them. I've got a similar feature in my  
application calling keywords. Some of my customers start praising  
when they see them, because they have a need, and for some other  
customers I try to explain and explain again and they don't get it.

Currently we need to find a solution for many requests, now we can  
think about "simply" using properties.


> * Bart, you talk about UNLIMITED space for properties.
>     You see need in A LOTS of properties?

Oh, come on, please don't limit them in ANY kind. I know a develop  
system with some kind of properties and two properties for an object,  
which are used for "custom" purposes. But for most objects the length  
are varies, some missed these properties and all these limits are not  
documented.

When using properties now in a more "automated way" then it's very  
tricky to guarantee to not reach a limit.


> * We also consider ability to access this properties as
>
>         SELECT ... WHERE tblPerson. at propName = 'dfsgsdfgd'

That sounds good, really good!


> Any more ideas?

Yes, when thinking about properties in a "class variable" way, then I  
didn't need to write a feature request for unique-id generation.


Btw. what happened with updates of properties in a system which is  
able to work in parallel tasks?????


regards

Thorsten Hohage
--
objectmanufactur.com - Hamburg,Germany




More information about the Valentina-beta mailing list