[jira] [Comment Edited] (QPID-7974) JdbcUtils.TableExists is very slow on big databases such as Oracle

["Adel Boutros (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209210#comment-16209210 ] 

Adel Boutros edited comment on QPID-7974 at 10/18/17 12:22 PM:
---------------------------------------------------------------

Hello Rob,

As it is the broker who tries to create the table, why don't we make all table names including the prefix forcibly in upper case? So the check will never fail.

Then if certain DB will still cause issues, we can have a special case for them.

What do you think?


was (Author: adelboutros@live.com):
Hello Rob,

What you are proposing will not fix the problem due to the fact we will always fallback to the existing code which is very slow.
As it is the broker who tries to create the table, why don't we make all table names including the prefix forcibly in upper case? So the check will never fail.

Then if certain DB will still cause issues, we can have a special case for them.

What do you think?

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org