On Wed, Aug 12, 2015 at 10:25 AM, Christian Mueller <
christian.muel...@os-solutions.at> wrote:
> Proposal:
> I will open a JIRA issue and prepare a pull request. All modifications
> will be done in DB2 specific classes. After publishing the pull request we
> can continue to discuss. Is this ok ?
Proposal:
I will open a JIRA issue and prepare a pull request. All modifications will
be done in DB2 specific classes. After publishing the pull request we can
continue to discuss. Is this ok ?
On Tue, Aug 11, 2015 at 2:19 PM, Andrea Aime
wrote:
> On Tue, Aug 11, 2015 at 1:40 PM, Christian Muel
On Tue, Aug 11, 2015 at 1:40 PM, Christian Mueller <
christian.muel...@os-solutions.at> wrote:
> Hi Andrea
>
> At the moment I do not have the knowledge for a general implementation and
> I am sure SQLServer,Oracle and DB2 have some differences. I would prefer to
> implement the logic in DB2Filter
Hi Andrea
At the moment I do not have the knowledge for a general implementation and
I am sure SQLServer,Oracle and DB2 have some differences. I would prefer to
implement the logic in DB2FilterToSQL. If somebody wants to introduce this
feature for another DB we can move common components to Filter
On Mon, Aug 10, 2015 at 2:38 PM, Christian Mueller <
christian.muel...@os-solutions.at> wrote:
> Hi all
>
> @Jody. Using DB2 I could detect which tables and columns participate in
> temporal support. I could implement the logic behind the scenes, no public
> API change necessary. I only wanted to
Hi all
@Jody. Using DB2 I could detect which tables and columns participate in
temporal support. I could implement the logic behind the scenes, no public
API change necessary. I only wanted to ask if we should make a concept for
all jdbc data stores.
@Andrea
Of course you could have timestamps in
On Sun, Aug 9, 2015 at 12:15 PM, Christian Mueller <
christian.muel...@os-solutions.at> wrote:
> Different DB implementations provide support for temporal data. An
> overview is here
>
> https://en.wikipedia.org/wiki/Temporal_database
>
> section
> Implementations in relational databases
>
> Here
Why not just use temporal if it is supported, and filter out the endpoint
if required in SQL? Or filter any extra results away on client side?
Should be able to keep this detail inside the DataStore without an extra
parameter. Can you detect if temporal is supported during initial
connection?
I a
Different DB implementations provide support for temporal data. An overview
is here
https://en.wikipedia.org/wiki/Temporal_database
section
Implementations in relational databases
Here is an example for the encoding of org.opengis.filter.temporal.During
The default geotools encoding in org.geot
