[jboss-jira] [JBoss JIRA] Closed: (JBAS-2273) createDDL for timers does not take care of pk-contraint-template

Dimitris Andreadis (JIRA) jira-events at lists.jboss.org
Thu Apr 12 12:51:59 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBAS-2273?page=all ]

Dimitris Andreadis closed JBAS-2273.
------------------------------------

    Resolution: Done

> createDDL for timers does not take care of pk-contraint-template
> ----------------------------------------------------------------
>
>                 Key: JBAS-2273
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2273
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Scheduling/Timers
>    Affects Versions: JBossAS-4.0.3 Final
>         Environment: JBoss 4.0.3RC3, JDK 1.5.0_05, Solaris/SPARC 9
>            Reporter: Frank Langelage
>         Assigned To: Dimitris Andreadis
>            Priority: Minor
>             Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4RC1
>
>         Attachments: diff.txt, GeneralPurposeDatabasePersistencePlugin.java
>
>
> I recently switched the persistence of timers and messages to an Informix datasource instead of hypersonic.
> The creation of table timers did not succeed, because the order of the constraint name for the PK and the PK's columns has to be just the other way round for informix. For CMP EJB's the is a pk-contraint-template in standardjbosscmp-jdbc.xml. I extended GeneralPurposeDatabasePersistencePlugin.java to use this.
> The modified file and the cvs diff will be attached shortly.
> A second issue was the datatype mapping for java.lang.Object.
> sql-type blob with informix means, you'll have to create an additional dbspace for blob data if you don't have one. The column's data will be stored there.
> As an alternative you can use datatype byte. The data will be stored inline with the table data in the same dbspace. This is, in my opinion, the better way. So I modified the informix type mapping for this type to jdbc-type LONGVARBINARY and sql-type BYTE.
> The cvs diff is also attached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list