452 ;;Quote: object-oriented databases better than relational ones for complex, hierarchical data structures such as Intermedia

452 ;;Quote: relational model more flexible because relationships defined by joins

452+;;Quote: relational model easier to use because of tabular data and ad hoc queries

453 ;;Quote: object-oriented databases good for complex, large-scale, data-intensive programs

453 ;;Quote: an object-oriented database has class definitions, uniquely named objects, and executable methods stored with each class

453 ;;Quote: while a relational database has one type; each object in an object-oriented database is assigned a class

453+;;Quote: a relational database has only one type, 'relation', with get and put operations on field values

453 ;;Quote: classes (i.e., data abstractions) define the behavior of objects in an object-oriented database; can change implementation without changing use classes which use the method

454 ;;Quote: object-oriented database can check method arguments at invocation instead of at transaction commit

454 ;;Quote: Intermedia will filter documents according to keywords attached to blocks and links

456 ;;Quote: the web object in Intermedia is the interface to the block and link database

462 ;;Quote: in a relational model, a hierarchy must be derived; in object-oriented model the hierarchy is defined in the database

462 ;;Quote: a relational database returns tuples for a query; applications may send updates to the database

462 ;;Quote: complex object networks require multiple relations that must be consistent with each other

463 ;;Quote: in object-oriented databases, the database itself manipulates the objects

464 ;;Quote: an Intermedia link is displayed as a marker; when selected, explainers are displayed

464+;;Quote: an Intermedia explainer is documentation associated with a link

464 ;;Quote: only markers in the current Intermedia web are displayed