On Dec 26, 2011, at 1:57 AM, Amit Tandon wrote:
Dear Karl
Foreign key is a good option (provided you use InnoDB database) to
automate
the deletion/updation of cart details when you remove cart.
Besides 1:1 cardinality is good or bad can only be decided on the
semantics
of your tables.
regds
amit
The difference between fiction and reality? Fiction has to make sense.
On Mon, Dec 26, 2011 at 1:55 PM, Karl DeSaulniers k...@designdrumm.comwrote:
On Dec 26, 2011, at 1:57 AM, Amit Tandon wrote:
Dear Karl
Foreign key is a good option (provided you use InnoDB
On Dec 26, 2011, at 3:05 AM, Amit Tandon wrote:
regds
amit
The difference between fiction and reality? Fiction has to make
sense.
On Mon, Dec 26, 2011 at 1:55 PM, Karl DeSaulniers k...@designdrumm.com
wrote:
On Dec 26, 2011, at 1:57 AM, Amit Tandon wrote:
Dear Karl
Dear KarlRefer Wiki
entryhttp://en.wikipedia.org/wiki/Entity-relationship_model.
The last diagram shows one to many relationship in many ways. That may help
you in clearing your doubts about the comma which is a way of representing
the relationship
Quoted from MS Access example
One-To-Many
Thank you!
On Dec 26, 2011, at 4:12 AM, Amit Tandon wrote:
Dear Karl
Refer Wiki entry. The last diagram shows one to many relationship in
many ways. That may help you in clearing your doubts about the comma
which is a way of representing the relationship
Quoted from MS Access example
Hello all,
I have two database tables. Cart and a cartdetails.
I want the information for the cartdetails to be based on/autofilled
info from cart.
I want the ability to delete from cart and cartdetails to
automatically clear as well.
Would a foreign key be best suited for this? What kind of
Dear Karl
Foreign key is a good option (provided you use InnoDB database) to automate
the deletion/updation of cart details when you remove cart.
Besides 1:1 cardinality is good or bad can only be decided on the semantics
of your tables.
As a an aside, if it is 1:1 cardinality, then you can
