Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I have learned more through this forum than I did on a two day course. Thanks to everyone for their help and other postings that I have found useful..."

Geography

Where in the world do Tek-Tips members come from?
supernova122 (MIS)
31 Oct 08 11:53
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 (MIS)
1 Nov 08 9:40
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 (Programmer)
3 Nov 08 9:01
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.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close