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 tables without the "temporal database/interval of validity" mode. If you want to use the temporal support you have to register the table/columns in the system catalog comparable to geometry columns. I am not an Oracle expert, but I am sure you can find the proper tables/columns in the system catalog. There is a special update/delete syntax but it is not necessary to use it. A short list of the features is here https://en.wikipedia.org/wiki/SQL:2011 Cheers Christian On Sun, Aug 9, 2015 at 9:37 PM, Andrea Aime <andrea.a...@geo-solutions.it> wrote: > 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 example for the encoding of org.opengis.filter.temporal.During >> >> The default geotools encoding in org.geotools.data.jdbc.FilterToSQL >> produces >> >> where ? between from and to (closed interval) >> >> DB2 would need >> >> where from <= ? and ? < to (semi closed interval) >> >> Oracle needs >> >> where from <= ? and (? < to or to is null) (semi closed interval >> including null value as open end) >> >> Some time ago, we had a discussion about the topic. >> http://sourceforge.net/p/geoserver/mailman/message/31706807/ >> >> My idea is to add a parameter USE_DB_TEMPORAL_MODEL to the datastore >> factory. This param defaults to false. If the param is true, the specific >> DB temporal support should be used. >> > > One thing I'm not sure about... can you can have timestamp in tables, > without enabling the "temporal database/interval of validity" mode on them? > It seems that in Oracle at least some special instructions have to be run: > > http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/12c/r1/ilm/temporal/temporal.html > > If this is the case, can't you have only some tables enabled that way, and > thus, require a per table support, in other > words, probably a hint? (althought... that might cause issues with > transactions, if special write semantics/syntax are needed too). > > Cheers > Andrea > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 339 8844549 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > ------------------------------------------------------- > -- DI Christian Mueller MSc (GIS), MSc (IT-Security) OSS Open Source Solutions GmbH
------------------------------------------------------------------------------
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
