Editing Object database (section)

==Technical features==
Most object databases also offer some kind of [[query language]], allowing objects to be found using a [[declarative programming]] approach. It is in the area of object query languages, and the integration of the query and navigational interfaces, that the biggest differences between products are found. An attempt at standardization was made by the [[Object Data Management Group|ODMG]] with the [[Object Query Language]], OQL.

Access to data can be faster because an object can be retrieved directly without a search, by following [[Pointer (computer programming)|pointers]].

Another area of variation between products is in the way that the schema of a database is defined. A general characteristic, however, is that the programming language and the database schema use the same type definitions.

Multimedia applications are facilitated because the class methods associated with the data are responsible for its correct interpretation.

Many object databases, for example Gemstone or VOSS, offer support for [[Version control|versioning]]. An object can be viewed as the set of all its versions. Also, object versions can be treated as objects in their own right. Some object databases also provide systematic support for [[database trigger|trigger]]s and constraints which are the basis of [[active database]]s.

The efficiency of such a database is also greatly improved in areas which demand massive amounts of data about one item. For example, a banking institution could get the user's account information and provide them efficiently with extensive information such as transactions, account information entries etc.