Using MG REST requests, when I use GET feature (http://xxx.FeatureSource/features.geojson/xxx/xxx) for features with TIMESTAMP data it returns json with date string: "TIMESTAMP '2016-08-20 22:34:52'" But when I update feature data with POST I need to have timestamp string formatted like that: "2016-08-20 22:34:52 I think it would be more consistent if GET features returns the same string form ("2016-08-20 22:34:52") as string format needed for POST requests. (Or is it by design?)
Also I noticed that GET feature request returns some fractions of the second from date fields which are not written in the feature source timestamp values, like that: "TIMESTAMP '2000-01-01 20:34:02.04601'" while real value is "TIMESTAMP '2000-01-01 20:34:02'" so fractions of the second comes from nowhere ? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/MG-REST-GET-Features-for-datetime-fields-tp5285762.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users