V4RB: Naming Convention for ObjectPtr-Link

Ruslan Zasukhin ruslan_zasukhin at valentina-db.com
Tue Apr 6 23:47:06 CDT 2010


On 4/7/10 7:29 AM, "Claudius Sailer" <claudius.sailer at me.com> wrote:

>>> for linking tbl_person and tbl_phones:
>>> 
>>> lnk_person_has_phone or lnk_phone_of_person
>>> 
>>> Actually we did not use the lnk_ part, but in retrospect it would have been
>>> better (easier to filter out what you need when working in the sql-editor)
>> 
>> Yes, this is the most common method to give names for links.
>> Can be even automated :)
> 
> 
> I do it now this way.
> 
> tablename_fieldname__referencetablename

Well, let me even more clarify.

Bart above have give name with some human sense.

Really automatd names are:

    link_T1_T2

I.e. We just show names of tables...

In theory between the same tables T1 and T2 can be few different  links.
Then name can be 

    link_T1_T2_N

Or add some sense word


In your above example, for me not clear why to add field name...
Link is something between tables... Link should not be related to fields.


> In the past I thought link and link name is internal database stuff, because I
> never worked or used this names. But now I am running on a problem and had to
> ALTER all ObjectPtr-Links and set a name.

> I am coming from V4RB 1.x through 2.x .... and so on, so I naver set a name in
> the past and missed the time when it was necessary to give a name for the
> links.

-- 
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]




More information about the Valentina mailing list