> It looks like the doc here > (https://wiki.jasig.org/display/CASUM/JpaTicketRegistry) is missing that > important piece of information for Oracle Ticket Registries: > > CREATE TABLE LOCKS ( > APPLICATION_ID VARCHAR(50) NOT NULL, > UNIQUE_ID VARCHAR(50) NULL, > EXPIRATION_DATE TIMESTAMP NULL > ); > ALTER TABLE LOCKS ADD CONSTRAINT LOCKS_PK > PRIMARY KEY (APPLICATION_ID);
That's intended to be a sample schema, but we ought to mention platform-specific issues like this one. I've updated the page to make it clear that it's an example and also a little note about the DATE issue on Oracle. I also noted that the use of JpaLockingStrategy avoids these issues altogether since it can create/update the schema automatically. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
