relationship implementation question

[supernova122]

I am developing asp.net using c# and SQL 2000 as backend database. I would like to know what is the best practice for class relationship implementation. Do I store the class in a Business Object table and the class relationship in a separate Relation Object table? What is the pros and cons? Or what is other better solution? I am in stage of design the object oriented database. Please advise and help me. Thanks.

 

[supernova122]

May be I should give an example. Say I have a product class and I use product table to store the attribute and another class supplier and I use supplier table. Now I want to store the relationship between product and supplier. Say the relationship is product is supplied by many suppliers and supplier supplies many products. What is the best practice to implement this relationships. Do I use another separate table to store these relationships or other better implementation? Please advise me. Thanks.

 

[jmeckley]

sql 2000 is a Relational Database Management System. it relates data, not objects. So using sql 2000 as an object relational database is like fitting a round peg in a square hole. here are some links on the subject.

if your talking about mapping relational objects to the an RDBMS then a framework like Hibernate(java) or NHibernate(.net) would be the best choice for mapping objects to data.

Jason Meckley
Programmer
Specialty Bakers, Inc.