activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1816) JDBC-Adapter: Inconsistent lower/uppercase of the database field TIME
Date Fri, 20 Jun 2008 16:29:00 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Davies resolved AMQ-1816.
-----------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

Resolved by SVN revision 669973

> JDBC-Adapter: Inconsistent lower/uppercase of the database field TIME
> ---------------------------------------------------------------------
>
>                 Key: AMQ-1816
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1816
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: Mario Siegenthaler
>            Assignee: Rob Davies
>             Fix For: 5.2.0
>
>   Original Estimate: 5 minutes
>  Remaining Estimate: 5 minutes
>
> The name of the database field ACTIVEMQ_LOCK.TIME is inconsistent in org.apache.activemq.store.jdbc.Statements:
in getCreateSchemaStatements() its name is "TIME" (upper case) while in getLockUpdateStatement()
it's called "time" (lower case). This causes problems with databases using a case-sensitive
collation.
> I suggest using the uppercase variant, since this is more consistent with the naming
of the other fields.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message