0
- Schema Changes: In an RDBMS modifying the database schema either by creating, updating or deleting tables is typically independent of the actual application. In an OODBMS based application modifying the schema by creating, updating or modifying a persistent class typically means that changes have to be made to the other classes in the application that interact with instances of that class. This typically means that all schema changes in an OODBMS will involve a system wide recompile. Also updating all the instance objects within the database can take an extended period of time depending on the size of the database.
- Language Dependence: An OODBMS is typically tied to a specific language via a specific API. This means that data in an OODBMS is typically only accessible from a specific language using a specific API, which is typically not the case with an RDBMS.
- Lack of Ad-Hoc Queries: In an RDBMS, the relational nature of the data allows one to construct ad-hoc queries where new tables are created from joining existing tables then querying them. Since it is currently not possible to duplicate the semantics of joining two tables by "joining" two classes then there is a loss of flexibility with an OODBMS. Thus the queries that can be performed on the data in an OODBMS is highly dependent on the design of the system.
Wiki User
∙ 14y ago
Add your answer:
Earn +20 pts
Are there any major similiarities between object oriented databases and relational databases?
In a Object Oriented Database, information is given in the form of objects as used in programming languages. "When database capabilities are combined with object programming language capabilities, the result is an object database management system (ODBMS). An ODBMS makes database objects appear as programming language objects in one or more object programming languages." (http://en.wikipedia.org/wiki/Object_database)"A relational database is a database that conforms to the relational model, and refers to a database's data and schema (the database's structure of how those data are arranged). Common usage of the term "Relational database management system" technically refers to the software used to create a relational database, but sometimes mistakenly refers to a relational database." (http://en.wikipedia.org/wiki/Relational_database)
A proportional model of three dimensional object?
A proportional model of a three dimensional object is an scale model.
What is a system based system?
A database system is a term that is typically used to encapsulate the constructs of a data model, database Management system (DBMS) and database .. (natsume)
How are the dimensions of a scale model related to the actual dimensions of the object?
When it is a scale model the model is proportional to the actual object only much smaller.
A proportional model of a three dimensional object?
the answer is scale model
List the advantage and disadvantage of database management system?
Answering "List the advantage and disadvantage of object oriented database model?" Answering "List the advantage and disadvantage of object oriented database model?"
Why firm shift from conventional database to object oriented database?
simplified standard model of database
Why object oriented database management gaining acceptance for developing applications and managing the hypermedia databases at business websites?
Why is the object -oriented database model gaining acceptance for developing applications and managing the hypermedia databases at business websites?
What is fuzzy database?
A fuzzy database incorporates fuzzy logic to handle imprecise or uncertain information. It allows for flexible querying and supports reasoning with vague or incomplete data. Fuzzy databases are useful in situations where traditional databases fall short due to their reliance on crisp, exact values.
Are there any major similiarities between object oriented databases and relational databases?
In a Object Oriented Database, information is given in the form of objects as used in programming languages. "When database capabilities are combined with object programming language capabilities, the result is an object database management system (ODBMS). An ODBMS makes database objects appear as programming language objects in one or more object programming languages." (http://en.wikipedia.org/wiki/Object_database)"A relational database is a database that conforms to the relational model, and refers to a database's data and schema (the database's structure of how those data are arranged). Common usage of the term "Relational database management system" technically refers to the software used to create a relational database, but sometimes mistakenly refers to a relational database." (http://en.wikipedia.org/wiki/Relational_database)
Structured types in object oriented database?
In object-oriented databases, structured types refer to user-defined data types that can be created to model complex objects with multiple attributes. These structured types are defined by specifying the attributes and their related data types, allowing for the creation of custom objects with specific properties. Structured types in object-oriented databases enable more flexibility and organization in representing complex data structures.
Limitations and benefits of rational database model?
One of the advantages of a relational database model is that the broken keys and records and the data complexity are usually simplified. The disadvantage of the relational database model is that it requires sophisticated processing power which is very costly.
What is the difference between object-oriented database and relational database?
A Relational Database is designed and maintained following some very well defined rules of logic and algebra. It often portrays a "one to many" relationship between two sets of data, and, less often, a "one to one" and "many to many" relation can be developed. An OO database uses less rigid design parameters, and can be adjusted design-wise to fit almost any kind of data environment. In fact, I'm not absolutely sure there is such a thing as an "object oriented" database, so much as there are database objects that are created and maintained with OO programming. I know that sounds self-referenceing, but that's OO for you... A relational database uses structure to locate and display data values, rather than programming logic. With a correctly designed RDB, finding and displaying data is very simple, compared to earlier network databases. Relational databases also permit the use of JOINS to merge and match sets of data ("relations"), to glean more information from your database that would normally be available.
What is the advantage of hibernate in j2ee?
Hibernate is capable of mapping all Object Oriented relationships (such as inheritance,interfaces, associations, composition, ternary associations) between objects. Hibernate follows both Bottom-up (existing database to OO model) and Top-down (OOModel to design the database schema) approaches: asanthine s
Define data models and list different types of data models?
A data model is a collection of concepts that can be used to describe the structure of a database and provides the necessary means to achieve this abstraction whereas structure of a database means the data types,relationships and constraints that should hold on the data. Data model are divided into three different groups they are 1)object based logical model 2)record based logical models 3)physical models Types: Entity-Relationship (E-R) Data Model Object-Oriented Data Model Physical Data Model functional data model
What is object oriented in c plus plus?
Object-oriented programming is a feature in C++ that allows you to better model real-world objects. An object is an instance of a class, which is a data structure in C++ that allows you to group different, but related types of data together.
Which are the different Classification of database management systems?
Database ClassificationDatabase systems are classified according to the way they represent data, i.e., on their provided data model. Broadly speaking, data models are classified intorecord-oriented and object-oriented models. There are three standardized record-oriented data models, namely, hierarchical, network,and relational. Although there is not a single object-oriented data model standard, as we discussed in 5.1.1 Object Relational Models, there are two objected-based approaches: namely, object-relational and object-oriented. Let us summarize these models.Hierarchical Data ModelThe hierarchical model stores the data records in a tree structure with edges that connect the different records representing their relationships. Except for the root, all other nodes must have a parent node and each node may have either zero, or more child (dependent) records. Thus, in the hierarchical model, relationships between record types can be only one-to-one or one-to-many binary relationships.IBM's IMS is possibly the only hierarchical DBMS in use today. There are only a few places where it is being used. In IMS, many-to-many relationships are handled by storing the data in two trees with opposite dependencies. Recursive relationships are handled in the same way. This means that the database contains redundant data, which is a waste of space, which makes the database structure inflexible to data change, and which makes the update operations more complex. Basic referential integrity of parent-child relationship is enforced by the DBMS.The hierarchical model does not support declarative query processing. Retrievals are achieved through navigationembedded within a high-level programming language. The navigation is a tree pre-order traversal that starts from the root and proceeds down the tree, accessing the subtrees in order from left to right. This means that users know and operate directly on the physical schema. Hence, the hierarchical model supports a low level of abstraction compared to relational and object-oriented models, and it also offers only weak security and integrity.Network Data ModelThe network model is similar to the hierarchical one in that it eliminates data redundancy in a database by storing the data in a graph (or network) structure rather than in a tree structure. In this way, recursive and circular relationships, for example, can be expressed with edges connecting two records of the same type.The basic one-to-many relationship is represented by connecting the dependent records together in an ordered linked list with the parent record, which is called the owner, at the head of the list. Records are permitted to contain more than one link. This capability is used in expressing many-to-many binary relationships between two record types. Many-to-many relationships are expressed with the help of intermediate records that can be directly linked with records of both the related record types, providing an indirect link between these records. (The use of intermediate records is called decomposition.) Basic referential integrity constraints are enforced by the DBMS.Similar to the hierarchical data model, the network model does not provide for declarative query processing. Access to records is achieved by navigation through the network structure using a set of predefined commands. These one-record-at-a-time commands must be embedded in a general-purpose programming language. Unlike records in the relational model, records in the network model can have fields, which are either single value, called simpleattributes, or multi-valued, called vector attributes.Relational Data ModelIn the relational model, data is stored in tables that completely hide the physical organization of data. Thus, compared to the hierarchical and network models, the relational model supports a high level of abstraction and a flexible database structure. The database structure, i.e., the schema, can easily be changed to accommodate new data and new access requirements.Relationships of any cardinality (1:1, 1:N, and N:M) and degree (binary, recursive, or higher order) can be expressed by means of foreign keys that are logical pointers. Binary 1:1 and 1:N, and binary recursive relationships, can be expressed directly, whereas high-order and N:M relationships can be expressed by decomposition, i.e., with the use of an intermediate table.In addition to basic referential integrity, the relational model supports semantic integrity constraints by means of checks, assertions, and triggers.Finally, as we have discussed in some detail, the relational model supports declarative, interactive query languages such as SQL and QBE. Furthermore, it can be embedded in almost any programming language, and therefore it supports the development of database application programs.Object-Oriented Data ModelThe object-oriented model supports a high level of abstraction and exhibits the same flexibility in specifying data relationships as the relational model. Relationships in the object-oriented model are expressed as references to object IDs. However, the object-oriented model offers more flexibility in specifying the schema of the database by means of complex types, user-defined types, user-defined functions, and object inheritance.Unlike the object-relational model, object-oriented data models are strongly tied to an object-oriented programming language (such as C++ and Smalltalk) acting as their data manipulation language. (In this respect, object-oriented models resemble the hierarchical and network models.) The object-oriented language is extended to support persistent objects whose values are stored in the database and can be shared with other programs. By manipulating transient and persistent objects uniformly, object-oriented models eliminate the so-called impedance mismatch; that is, object-oriented models can thus eliminate any incompatibility between the declarative database manipulation language and the procedural application programming language that is due to difference in programming paradigms and type systems. Thus, object-oriented databases simplify the task of programming by supporting a single level storage and a computationally complete DDL/DML.In order to support declarative and interactive query processing, the ODMG standardization treats the object-relational model as a special object-oriented model, implementing its declarative query language.
