Benefits of declaring foreign key links.

[Ruslan Zasukhin]

On 12/23/05 6:25 PM, "Ed Kleban" <Ed at Kleban.com> wrote:

>>> The other reason I am tempted to do this is that I see the advantage of
>>> having these links explicitly declared so that Valentina Studio will show
>>> the related links in the Data Browser.
>> 
>> Right. 
>> 
>> Hmm, not right. IF you have also create FOREIGN KEY on your byte fields,
>> then Vstudio also will show links.
> 
> Yes. I'm aware of that.  And the reason behind these questions is to better
> understand whether I should keep the UByte and UShort fields and continue to
> use them as pointers manually along with declaring them as links so that VS
> will see and use them....
> 
> Or whether there is some additional benefit to instead using ObjectPtr
> fields instead because of some performance gain I am unaware of at the cost
> of using a lot more storage.
>  
> So far my conclusion based on what I've read here is that there is no real
> advantage to using an ObjectPtr over using a smaller-sized UByte or UShort
> rid reference field AS IF it were a BytePtr or ShortPtr in my code, and
> declaring it to be a foreign key link with the RecId of the parent table
> being the key field.
> 
> That make sense?

Hard to say. 

I think can exists db where small win,
and can exists case when ObjectPtr win.

You can do benchmarks self

Actually in DB I meet this always. Exists always few  cases and few
algorithms, each win in its are.


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