CSC/ECE 517 Summer 2008/wiki3 1 th: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
It would be good if o-o programs could interact with o-o databases, but alas, relational databases have a 99% market share. This has led to many attempts to access them from o-o languages. Design patterns for doing this have been developed, starting with "crossing chasms" and extending to Rails' ActiveRecord. Investigate the various approaches for marrying o-o programs to relational databases, comparing them in terms of ease of programming, robustness, and efficiency. | It would be good if o-o programs could interact with o-o databases, but alas, relational databases have a 99% market share. This has led to many attempts to access them from o-o languages. Design patterns for doing this have been developed, starting with "crossing chasms" and extending to Rails' ActiveRecord. Investigate the various approaches for marrying o-o programs to relational databases, comparing them in terms of ease of programming, robustness, and efficiency. | ||
=Overview= | |||
=Approaches= | |||
=Comparison= | |||
==Ease of Programming== | |||
==Robustness== | |||
==Efficiency== | |||
=Summary= | |||
=Links= | |||
http://www.google.com/search?hl=en&q=ORM&btnG=Google+Search | |||
Revision as of 23:34, 22 July 2008
RDB/OO Patterns
It would be good if o-o programs could interact with o-o databases, but alas, relational databases have a 99% market share. This has led to many attempts to access them from o-o languages. Design patterns for doing this have been developed, starting with "crossing chasms" and extending to Rails' ActiveRecord. Investigate the various approaches for marrying o-o programs to relational databases, comparing them in terms of ease of programming, robustness, and efficiency.