Item Oriented Databases .

Uploaded on:
Object-Oriented Databases. Object Orientation. Object Orientation Set of design and development principles Based on autonomous computer structures known as objects OO Contribution areas Programming Languages Graphical User Interfaces Databases Design Operating Systems.
Slide 1

Question Oriented Databases

Slide 2

Object Orientation Object Orientation Set of outline and improvement standards Based on self-governing PC structures known as articles OO Contribution regions Programming Languages Graphical User Interfaces Databases Design Operating Systems

Slide 3

Evolution of OO Concepts originate from protest situated programming dialects (OOPLs) Ada, ALGOL, LISP, SIMULA OOPLs objectives Easy-to-utilize advancement environment Powerful demonstrating devices for advancement Decrease being developed time Make reusable code OO Attributes Data set not latent Data and techniques bound together Objects can follow up on self

Slide 4

OO Concepts: Objects Abstract representation of a certifiable element Unique personality Embedded properties Ability to associate with different items and self OID Unique to protest Not an essential key Attributes Called occurrence factors Domain Object state Object values at any given time

Slide 5

OO Concepts: Objects (con\'t.) Methods Code that performs operation on question\'s information Has name and body Messages Invokes strategy Sent to question Classes Collection of comparable items Shares qualities and structure Protocol Represents question\'s open viewpoint

Slide 6

OO Concepts: Objects (con\'t.) Class progressive system Code that performs operation on protest\'s information Has name and body

Slide 7

Characteristics of OODM Supports complex articles Must be extensible Supports epitome Exhibit legacy Supports question personality

Slide 8

OO versus E-R Model Components Table 11.3

Slide 9

Referential Sharing of Objects

Slide 10

Class-Subclass Relationship

Slide 11

Interobject Relationships Attribute-Class Link Object\'s trait references another question Relationship Representation Related classes encased in boxes Double line on right side shows compulsory Connectivity demonstrated by naming every container 1:M M:N with an Intersection Class

Slide 12

1:1 and 1:M Relationships

Slide 13

Employee-Dependent Relationship

Slide 14

Representing the M:N Relationship

Slide 15

Late and Early Binding Late restricting Data sort of property not known until runtime Allows distinctive examples of same class to contain diverse information sorts for same quality Early restricting Allows database to check information sort at gathering or definition time

Slide 16

OODM versus E-R Data Models Object, Entity, and Tuple OODM question has conduct, legacy, and epitome OO demonstrating more normal Class, Entity Set, and Table Class permits portrayal of information and conduct Class permits dynamic information sorts Encapsulation and Inheritance Object acquires properties of superclasses Encapsulation shrouds information representation and strategy

Slide 17

Object ID Not upheld in social models Relationships OODM Interclass references Class chain of importance legacy Relational models Value-based approach Access Relational models SQL OODM Navigational Set-situated get to OODM versus E-R Data Models (con\'t.)

Slide 18

OODBMS Database administration framework coordinates advantages of average database frameworks with OODM qualities Handles a blend of information sorts Follows OO rules Follows DBMS rules

Slide 19

OO and Database Design Provides information recognizable proof and the strategies for information control Data and techniques independent element Iterative and incremental DBA accomplishes all the more programming Lack of benchmarks

Slide 20

OODBMS Advantages More semantic data Support for complex items Extensibility of information sorts May enhance execution with effective reserving Versioning Reusability Inheritance speeds improvement and application Potential to incorporate DBMSs into single environment

Slide 21

OODBMS Disadvantages Strong resistance from the built up RDBMSs Lack of hypothetical establishment Throwback to old pointer frameworks Lack of standard specially appointed question dialect Lack of business information outline and administration instruments Steep expectation to learn and adapt Low market nearness Lack of similarity between various OODBMSs

Slide 22

OO Influences on Relational Model Extensibility of new client characterized (conceptual) information sorts Complex articles Inheritance Procedure calls (principles or triggers) System-created identifiers (OID surrogates)

Slide 23

The Next Generation of DBMS Object-arranged database frameworks Artificial knowledge frameworks Expert frameworks Distributed database The Internet

View more...