Building Java Enterprise Applications

Events and Scheduling

With the user and accounts stores in place, all that’s left to add to the core database schema is the storage for events. This includes the EVENTS and ATTENDEES table. The scripts in this section are database-specific versions of the SQL script shown in Example 3-4.

Cloudscape

Example A-11 is the Cloudscape version of the SQL script that creates the events and scheduling storage.

Example A-11. SQL Script for Creating the Events Store on Cloudscape Databases

-- EVENTS table
CREATE TABLE EVENTS (
       EVENT_ID             INT PRIMARY KEY NOT NULL,
       DESCRIPTION          VARCHAR(50) NOT NULL,
       DATE_TIME            DATE NOT NULL
);

-- ATTENDEES table
CREATE TABLE ATTENDEES (
       USER_ID              INT NOT NULL,
       EVENT_ID             INT NOT NULL,
       CONSTRAINT AT_USER_ID_FK FOREIGN KEY (USER_ID)
         REFERENCES USERS (USER_ID),
       CONSTRAINT EVENT_ID_FK FOREIGN KEY (EVENT_ID)
         REFERENCES EVENTS (EVENT_ID)
);

InstantDB

The InstantDB-specific SQL for creating the events store is shown in Example A-12.

Example A-12. SQL Script for Creating the Events Store on InstantDB Databases

; Load InstantDB JDBC drivers d org.enhydra.instantdb.jdbc.idbDriver; o jdbc:idb=forethought.prp; ; EVENTS table e CREATE TABLE EVENTS ( EVENT_ID INT PRIMARY KEY NOT NULL, DESCRIPTION VARCHAR(50) NOT NULL, DATE_TIME DATE NOT NULL ); ; ATTENDEES table e CREATE TABLE ATTENDEES ( USER_ID INT NOT NULL, EVENT_ID INT NOT NULL, CONSTRAINT AT_USER_ID_FK FOREIGN KEY (USER_ID) REFERENCES USERS (USER_ID), CONSTRAINT EVENT_ID_FK FOREIGN KEY (EVENT_ID) REFERENCES EVENTS (EVENT_ID) ...