If the application has to deliver these objects then the database has to store them. The traditional relational database was designed to store basic data with strict rules concerning the relation of a say a title to the authors responsible for it. Now a database has to store a Web page or Java Applet along with the rules for its subsequent use. Oracle for instance has announced several new features within Oracle8 and the associated developer tools to handle objects. As some vendors have moved towards Oracle, DRA, with Taos, has jumped a level and gone straight to an object oriented database architecture.
Libraries have to take a long view in everything that they do.
Those vendors who have isolated the DBMS structure from the application will have the most convincing answer to the first question since they should be able to move easily to a new DBMS supplier - Amicus for example has already migrated from Ingres to Oracle. Vendors using their own proprietary database have to worry more about whether they have the resources to re-engineer for objects and other industry developments as the pace of change increases. Table showing database used by library systems - these figures are derived from the table of products and databases in the database technology briefing. In addition, April 15 th will see the release details of version 8.1 of Oracle which will feature a Java virtual machine for executing Java triggers in the database. Both Informix and Sybase have announced similar features.