[ https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_36006 ]
Hiram Chirino commented on AMQ-660: ----------------------------------- Hi Johan, Yeah, I don't think the delete query can be changed much. We pass in a a parameter (current time as long) to the query and I can't think of a way using the parameter but not really use against the query. The upside is that even if your expiration field is not indexed, if you don't have tons of data in the DB then the query should not take that long to do a tablescan. > Add support for MaxDB > --------------------- > > Key: AMQ-660 > URL: https://issues.apache.org/activemq/browse/AMQ-660 > Project: ActiveMQ > Type: New Feature > Components: Message Store > Reporter: Hiram Chirino > Assignee: Hiram Chirino > Fix For: 4.0 RC3 > Attachments: activemq.log, activemq.log > > > Originaly reported on the user mailing list: > http://www.nabble.com/Adding-support-for-MaxDB-in-ActiveMQ-JDBC-persistence-layer-t1334466.html#a3572564 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
