[
https://issues.apache.org/activemq/browse/AMQ-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58634#action_58634
]
Dejan Bosanac commented on AMQ-2681:
------------------------------------
Patch applied with svn revision 930206. Thanks Ying.
GenerateJDBCStatements is useful, but it would be even more useful if it would
use specified database dialect as persistence adapters do. You can take a look
at JDBCPersistenceAdapter.start() for example on how it can be done. Also, it'd
be good to have this as an option that could be executed from the command line,
so that folks can create statements, when they're deploying the broker (maybe
activemq-admin command with some new switch). Interested in implementing some
of these?
Cheers
> set findMessageStatement cause problem for JDBCPersistenceAdapter due to
> error in Statements.java
> -------------------------------------------------------------------------------------------------
>
> Key: AMQ-2681
> URL: https://issues.apache.org/activemq/browse/AMQ-2681
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.1
> Reporter: ying
> Assignee: Dejan Bosanac
> Priority: Blocker
> Fix For: 5.4.0
>
> Attachments: AMQ-2681-2-trunk.patch, AMQ-2681.patch
>
>
> field findMessageByIdStatement in
> org.apache.activemq.store.jdbc.Statements.java is never used and
> getFindMessageByIdStatement is using findMessageStatement which causes
> problem. Because if someone overwrite the default findMessageStatement, it
> will cause doGetMessageById to fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
