Re: [Geotools-devel] Improvement for SQL Views (Virtual Tables)

On Wed, Mar 7, 2018 at 5:50 PM, Nuno Oliveira < nuno.olive...@geo-solutions.it> wrote: > Indeed Teradata and SQLServer dialects pagination handling are quite > complex. > As far I can tell they should work fine. > Awesome. Then I have no objection, it's a good feature in the right hands. Just

Re: [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Indeed Teradata and SQLServer dialects pagination handling are quite complex. As far I can tell they should work fine. On 03/07/2018 03:57 PM, Andrea Aime wrote: On Wed, Mar 7, 2018 at 4:53 PM, Nuno Oliveira > wrote:

Re: [Geotools-devel] Improvement for SQL Views (Virtual Tables)

On Wed, Mar 7, 2018 at 4:53 PM, Nuno Oliveira < nuno.olive...@geo-solutions.it> wrote: > 2) The SQL View mechanism is generic, cross database... will whatever > query location work along with paging and query hints across > all databases? What I'm asking here is to consider all JDBCDataStore

Re: [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Hi Andrea, thanks for the feedback, please see my answers bellow :) On 03/07/2018 03:25 PM, Andrea Aime wrote: Hi Nuno, not against but I have a couple of worries. 1) The where clause generated by GeoServer talks about attributes visible when the full query is run, depending on the query

Re: [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Hi Nuno, not against but I have a couple of worries. 1) The where clause generated by GeoServer talks about attributes visible when the full query is run, depending on the query complexity one might decide to place the where somewhere that only has a subset of such attributes computed (e..g, case

Re: [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Sounds good to me Ian On 7 March 2018 at 14:59, Nuno Oliveira wrote: > Hi all, > > Sorry for the cross porting but this touches the two projects ... > > I would like to extend the current support of SQL views (Virtual Tables) > to > allow us to add a placeholder