Title: Message Title
Andrea Aime [Administrator] created an issue
On Fri, Aug 7, 2015 at 9:57 PM, Ben Caradoc-Davies b...@transient.nz wrote:
Thanks for the confirmation. My guess is that this is something needed
for multiply mapped types or feature chaining and that
getFeatureSourceByName could have an even more longwinded method name
like
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
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
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 is an
Out of the alternatives the safest approach seems to turn this off by
default, and then allow it to be enabled with a query hint.
--
Jody Garnett
On 9 August 2015 at 00:26, Andrea Aime andrea.a...@geo-solutions.it wrote:
On Sun, Aug 9, 2015 at 7:57 AM, Jody Garnett jody.garn...@gmail.com
