tables and binary links

[Ruslan Zasukhin]

On 9/2/07 6:53 PM, "Bart Pietercil" <bart.pietercil at gmail.com> wrote:

Hi Bart,

> could somebody please confirm that I understood the use of tables and
> binary links correctly in this case
> 
> Schema:
> 
> Organisations --> cells <----members (personnel)

So cells is MANY to MANY link table, right?
 
> one additional table "listvalues"
> 
> rec_id,list_id,menuvalue



> cells in classic db design would have been something like this
> 
> cell_id (pk)
> cell_name (varchar)
> fk_org (fk)
> cell_type = alistvalue
> cell_status = another listvalue
> parent_cell_id --> selfrelation to get a hierarchy structure


---------
> in valentina using binary links this (I think) would be
> 
> Table cells
> 
> cell_name
> 
> binary links
> lnk_org:organisation 1:M cells
> lnk_celltype:listvalues 1:M cells
> lnk_cellstatus:listvalues 1:M cells
> lnk_parent:cells 1:M cells
> 
> So I only have 1 field and 4 binary links
> 
> Have I understood this correctly (or is it back to the manual?)

I afraid binaryLink will not work here. I need to think on your tables
little more.

What is 100% clear is

* you can drop PK 
* instead of FK to use ObjectPtr fields

> cell_name (varchar)
  Org_PTR

  cell_type = alistvalue            <-- what is this?
  cell_status = another listvalue   <-- also FK to table listvalues?

  parent_cell_PTR --> selfrelation to get a hierarchy
                       also ObjectPtr


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