Skip to main content
7 events
when toggle format what by license comment
Dec 7, 2018 at 15:33 comment added Vince They deprecated the API, so the documentation is sparse, at best.
Dec 7, 2018 at 4:55 comment added Son of a Beach Thanks Vince. So if I understand you correctly, you're saying that ArcGIS SDE geodatabases cannot store a datetime with any more precision that whole seconds? (Even when the underlying RDBMS datatype can.) Can you direct me to any documentation for the ArcGIS side of this?
Dec 7, 2018 at 4:53 comment added Vince Enterprise geodatabases bind datetime data types through struct tm, which stores seconds using an integer. The decimal values you're seeing are due to floating point representation issues.
Dec 7, 2018 at 3:30 comment added Son of a Beach By coincidence, while I was writing that last comment, I got a phone call from ESRI (Australia) support (I'd logged an issue with them yesterday). They have been able to replicate the problem and they think it may be an ArcGIS bug.
Dec 7, 2018 at 3:24 comment added Son of a Beach I've looked in SQL Server, and ArcGIS has definitely created the field as a 'datetime2' field type. It is NOT a 'datetime' field type. So it should me more than capable of this precision.
Dec 7, 2018 at 3:18 comment added Michael Stimson Perhaps this will illuminate stackoverflow.com/questions/36414315/… . Although you're using GIS software you have to work within the constraints of the database data types. Note: I have no idea what will happen to your SDE data if you change the field type as described, it may work fine or cause the field/featureclass to be unrecognizable it is impossible to tell until you actually try - then please answer your own question with this valuable information for future users.
Dec 7, 2018 at 2:57 history asked Son of a Beach CC BY-SA 4.0