CSC/ECE 517 Fall 2010/ch2 2a aa: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
---- | ---- | ||
#Introduction to | #Introduction to Object Relational Mapping. | ||
#Why ORM, why not another solution? | #Why ORM, why not another solution? | ||
#Flavors of ORM. | #Flavors of ORM. | ||
| Line 23: | Line 23: | ||
== Introduction to | == Introduction to Object Relational Mapping. == | ||
Object Relational Mapping is a technique of mapping the solution entities of an object oriented system, [http://en.wikipedia.org/wiki/Object_%28computer_science%29]objects to [http://en.wikipedia.org/wiki/Relational_database_management_system] relational database tables. This technique came into existence as an answer to the problem of lack of persistence of objects across session in [http://en.wikipedia.org/wiki/Object-oriented_programming]Object Oriented Programming Systems. For instance in a software solution to manage the order and inventory systems of a company, the objects that are part of the systems (orders, customers . . .) must be accessible even if the system was temporarily shut down for a while. [http://en.wikipedia.org/wiki/Object-relational_mapping]ORM helps in achieving this very essential requirement by bringing the database into the picture, more specifically bringing the RDBMS into the picture. | Object Relational Mapping is a technique of mapping the solution entities of an object oriented system, [http://en.wikipedia.org/wiki/Object_%28computer_science%29]objects to [http://en.wikipedia.org/wiki/Relational_database_management_system] relational database tables. This technique came into existence as an answer to the problem of lack of persistence of objects across session in [http://en.wikipedia.org/wiki/Object-oriented_programming]Object Oriented Programming Systems. For instance in a software solution to manage the order and inventory systems of a company, the objects that are part of the systems (orders, customers . . .) must be accessible even if the system was temporarily shut down for a while. [http://en.wikipedia.org/wiki/Object-relational_mapping]ORM helps in achieving this very essential requirement by bringing the database into the picture, more specifically bringing the RDBMS into the picture. | ||
== Why ORM, why not another solution? == | |||
Revision as of 00:29, 21 September 2010
Language extensions for ORM
- Introduction to Object Relational Mapping.
- Why ORM, why not another solution?
- Flavors of ORM.
- ORM implementation in specific languages
- Groovy, Grails and GROM
- Creating classes and tables
- Basic CRUD
- Creating objects
- Reading objects
- Updating objects
- Deleting objects
- PHP
- Creating classes and tables
- Basic CRUD
- Creating objects
- Reading objects
- Updating objects
- Deleting objects
- Groovy, Grails and GROM
Introduction to Object Relational Mapping.
Object Relational Mapping is a technique of mapping the solution entities of an object oriented system, [1]objects to [2] relational database tables. This technique came into existence as an answer to the problem of lack of persistence of objects across session in [3]Object Oriented Programming Systems. For instance in a software solution to manage the order and inventory systems of a company, the objects that are part of the systems (orders, customers . . .) must be accessible even if the system was temporarily shut down for a while. [4]ORM helps in achieving this very essential requirement by bringing the database into the picture, more specifically bringing the RDBMS into the picture.