	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.7

OOP: Data Objects Design Pattern For Cascading

Asked by CyrexCore2k in C# Programming Language, Algorithms, SQL Query Syntax

Tags: OOP, Data Object, Business Object, Database, Table, Binding

I was curious if anyone had suggestions for the following problem I've been having.

Say I have the following tables in a database:

TABLE Images
{
imageid int,
location varchar(50)
}
TABLE Users
{
userid int,
imageid int
}
TABLE Games
{
gameid int,
userid int,
imageid int
}

My question is, what would be a good design for gathering the information for a game, the image associated with that game, the user who created the game and the image associated with that user?

Lately my designs have design patterns similar to those below. However, since the Game object's image and the User object's image are going to be different I can't think of a scalable why to create all four objects (User, Game and two Image objects) using the results from a single query since the naming conventions will inevitably collide. Consider the case:

SELECT g.*, u.*, gi.*, ui.*
FROM Games g
INNER JOIN Users u ON g.userid = u.userid
INNER JOIN Images gi ON g.imageid = gi.imageid
INNER JOIN Images ui ON u.imageid = ui.imageid
WHERE g.gameid = 1

Has anyone figured out a clever way to handle this kind of thing? I'd really like a scalable way to cascade object generation from a single query even in the event that multiple objects are gathering data from the same table.

View the Solution FREE for 30 Days

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:

           
           
             //In Image class:
Image CreateFromReader(SqlDataReader dr)
{
   Image ret = new Image();
   ret.imageid = int.Parse(dr["imageid"].ToString());
   ret.location = dr["location"].ToString();
   return ret;
}
 
// In User class:
User CreateFromReader(SqlDataReader dr)
{
   User ret = new User()
   ret.userid = int.Parse(dr["userid"].ToString());
   ret.image = Image.CreateFromReader(dr);
   return ret;
}
 
// In Game class:
Game CreateFromReader(SqlDataReader dr)
{
   Game ret = new Game();
   ret.gameid = int.Parse(dr["gameid"].ToString());
   ret.image = Image.CreateFromReader(dr);
   ret.user = User.CreateFromReader(dr);
   return ret;
}
           
         

20091111-EE-VQP-92 - Hierarchy / EE_QW_EXPERT_20070906

Hall of Fame

1. abel587,372
2. ragi0017421,358
3. TheLearn...345,594
4. anarki_ji...286,340
5. Idle_Mind283,576
6. jaime_oliv...244,139
7. MogalManic237,860
8. Dhaest234,933
9. kaufmed218,888
10. Fernando...208,644
11. daveamour176,106
12. guru_sami165,122
13. angelIII159,742
14. emoreau157,530
15. pivar152,031
16. mas_oz...148,624
17. daryal132,690
18. djjaries121,873
19. philipjonat...119,218
20. p_davis114,393
21. mrjoltcola113,138
22. ToddBeau...108,018
23. nmarun107,525
24. jinal104,197
25. Omego2K102,314

1. TheLearn...2,677,701
2. gregoryyo...1,422,807
3. jaime_oliv...1,365,459
4. Fernando...1,016,700
5. AlexFM994,109
6. Idle_Mind980,082
7. ragi0017826,421
8. angelIII732,688
9. gauthampj726,247
10. anarki_ji...717,610
11. dstanley9713,657
12. TheAvenger653,871
13. abel624,502
14. JimBrandley596,614
15. emoreau565,778
16. Dhaest557,024
17. Zephyr__442,269
18. MogalManic381,587
19. p_davis370,522
20. REA_AN...366,519
21. carl_tawn359,852
22. surajguptha359,057
23. Desp351,128
24. sumix328,743
25. _TAD_318,360

OOP: Data Objects Design Pattern For Cascading

Asked by CyrexCore2k in C# Programming Language, Algorithms, SQL Query Syntax

Tags: OOP, Data Object, Business Object, Database, Table, Binding

About this solution