Object database: Difference between revisions

Revision as of 04:33, 10 October 2012

Revision as of 04:36, 10 October 2012

Line 20:

The first school of thought is in reality is rare as will underlining database design is inefficient, as it is often spread over several separate database tables. For example if class 'Foo' extends class 'Bar', then the data defined within 'Foo' would be within one table and the data for 'Bar' would be within another, this separation is essential as class 'Goo' that also extends class 'Bar' will share the same 'Bar' table. This design then requires multiple reads, lock, logs and writes and can slow all transaction down.

The second school of thought is often done within industry standard SQL database by using a standard text fields, however this does have the effect of locking away the data held within as [[Sql|SQL]] only understands single or [[Comma-separated_values|comma separated values]]. Object Databasedatabases ofapplying this school of thought will allow for databasedata to be encoded in a hierarchical manner, while still allowing data to be [[Database_index|indexed]].

==History==