>Working on the basis that anything from David Crozir Esq is worthy of a

>read, here is an article re differences between their database V

>Database the Relational Way:

>http://www.valentina-db.com/en/developer-articles/104-5-minute-technical-intro-to-valentina

From the article:

"Valentina does not require the creation of KEY fields - you can avoid the

headache of filling in unique values.

Each Valentina Table has a special RecID field, which provides a unique

number for a record of this table.

...

To establish the all important M:M link between these two tables, Valentina

offers a very special feature: the BinaryLink.

CREATE BINARY LINK PersonPhone(Person, Phone)

AS MANY TO MANY

...

Versus Primary Keys. RecID fields do not consume any disk space. Compare

this with a primary key with associated indexes.

...

If designed with the native Valentina Object-Relational way, you would

execute the same query with Valentina:

SELECT *

FROM Person JOIN Phone"

Okay, yeah, but nothing is free.

SOME space SOMEWHERE on the disk is being used to store those invisible

RecID values.

And, what special hoops do I have to jump through in my code during data

entry so that Valentina knows WHICH phone goes with WHICH person?

It sure isn't going to guess it unless I follow a pretty strict protocol

for the data entry.

Ken Dibblewww.stic-cil.org

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/5.2.1.1.1.20111214205830.01f53318@POP-Server.stny.rr.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.