[
https://issues.apache.org/jira/browse/QPID-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209171#comment-16209171
]
Rob Godfrey commented on QPID-7974:
-----------------------------------
So IIRC there were (4 years ago) issues with RDBMS that were not case sensitive
in their table names on some platforms (I have vague memories of this being the
reason why the code is how it is). We don't really do adequate testing of this
code across different RDBMS and operating systems to see if this would cause a
regression. I guess the common case is that the table exists, so we could
alter the code to do the check with the table name in, and if that fails revert
to the existing code - obviously that might still cause a 12 minute delay every
time you start the broker against an empty DB - would that be an issue for you?
> JdbcUtils.TableExists is very slow on big databases such as Oracle
> ------------------------------------------------------------------
>
> Key: QPID-7974
> URL: https://issues.apache.org/jira/browse/QPID-7974
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-6.1.4
> Reporter: Adel Boutros
>
> The problem is that JdbcUtils.tableExists will actually load all tables and
> then iterate to find the correct one. On Oracle, this can be around 40 000
> tables. So it will take 12 minutes for the broker to start.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
