[jboss-jira] [JBoss JIRA] Updated: (JBAS-4042) Timer service fails to create TIMERS table is table exists in other schema

[Dimitris Andreadis (JIRA)]

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

Dimitris Andreadis updated JBAS-4042:
-------------------------------------

       Issue Type: Feature Request  (was: Bug)
    Fix Version/s: JBossAS-4.2.0.GA
                    JBossAS-5.0.0.Beta3
                   JBossAS-4.0.5.SP1 
                       (was: JBossAS-4.2.1.CR1)

> Timer service fails to create TIMERS table is table exists in other schema
> --------------------------------------------------------------------------
>
>                 Key: JBAS-4042
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4042
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Scheduling/Timers
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: Reported against Oracle 9i
>            Reporter: Darran Lofthouse
>         Assigned To: Dimitris Andreadis
>             Fix For: JBossAS-4.0.5.SP1 , JBossAS-4.2.0.GA,  JBossAS-5.0.0.Beta3
>
>
> The TIMER service does not allow the name of the table to be used by the timer service to be overriden.
> To check is the table already exists the following is called: -
> rs = dmd.getTables(catalog, schema, tableName, null);
> return rs.next();
> For the timer service no schema is specified so this returns the TIMER tables for all schemas so we do not create the table for the current schema even though it is not available.
> If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be restricted to the schema so will prevent tables from other schemas being picked up.

-- 
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