oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Barber (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OODT-460) DataSourceCatalog doesn't work with MySQL
Date Wed, 28 Aug 2013 15:56:52 GMT

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

Tom Barber commented on OODT-460:
---------------------------------

I work with similar issues in my day job and we have a dialect layer that dictates what certain
database supports and doesn't that then allows the software to create the correct SQL for
the database, I would suggest a simlar setup here that allows people to plugin different database
dialects when they want to support a different database, and a "generic" dialect for anything
thats not supported.
                
> DataSourceCatalog doesn't work with MySQL
> -----------------------------------------
>
>                 Key: OODT-460
>                 URL: https://issues.apache.org/jira/browse/OODT-460
>             Project: OODT
>          Issue Type: Bug
>          Components: file manager
>    Affects Versions: 0.3
>         Environment: none
>            Reporter: Brian Foster
>             Fix For: 0.7
>
>
> It appears when support was added for BooleanQueries we lost support with MySQL.
> Either a INTERSECT substitute which is supported across the board can be used or maybe
just turn DataSourceCatalog into OracleDataSourceCatalog and then create a MySqlDataSourceCatalog
(this way each can be further customized to use custom statements for each to gain speed improvements)...
then possible find some happy medium command for INTERSECT and have DataSourceCatalog use
that -- in other words, this issue will split DataSourceCatalog into 3 classes:
> DataSourceCatalog : generic data source catalog (not neccessarily fast or pretty, but
works for all SQL DBs)
> OracleDataSourceCatalog : customized for speed and use with Oracle specifically
> MySqlDataSourceCatalog : customized for speed and use with MySQL specifically 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message