sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M. Le Bihan (JIRA)" <j...@apache.org>
Subject [jira] [Work started] (SIS-304) Attempt to use Calcite SQL Parser instead of the one currently used to parse SQL statements
Date Mon, 07 Dec 2015 08:09:11 GMT

     [ https://issues.apache.org/jira/browse/SIS-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Work on SIS-304 started by M. Le Bihan.
---------------------------------------
> Attempt to use Calcite SQL Parser instead of the one currently used to parse SQL statements
> -------------------------------------------------------------------------------------------
>
>                 Key: SIS-304
>                 URL: https://issues.apache.org/jira/browse/SIS-304
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: Shapefile
>    Affects Versions: 0.7
>            Reporter: M. Le Bihan
>            Assignee: M. Le Bihan
>              Labels: Calcite, JDBC
>
> The current SQL parser developped with DBase III JDBC driver has many limitations, and
it can only works for simple SELECT statements.
> The [Calcite|http://calcite.apache.org] open source project might be of great help if
it matches our need.
> This task is a PoC that if it goes well, will allow the removal of 
> org.apache.sis.internal.shapefile.jdbc.sql.CrudeSQLParser
> org.apache.sis.internal.shapefile.jdbc.sql.ConditionalClauseResolver
> org.apache.sis.internal.shapefile.jdbc.sql.ClauseResolver
> in favor of the Calcite API



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message