| Numéro d’ID de bogue |
BUG-000159745 |
| Envoi | July 8, 2023 |
| Dernière modification | November 16, 2025 |
| S’applique à | ArcGIS Pro |
| Version trouvée | 3.1.2 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 11.0 64 bit |
| Statut | As Designed
Après examen par l’équipe de développement, il a été déterminé que ce comportement est prévu. Pour plus d’informations, reportez-vous à la section Informations supplémentaires.
|
Informations supplémentaires
Please refer to https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-oracle/data-types-oracle.htm and https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/data-types-sqlserver.htm for information on how, in ArcGIS, the float and double data types are stored in enterprise geodatabases on Oracle or SQL Server. The difference between these types at the DBMS level is entirely based on the values of precision & scale. The data type itself is the same number for Oracle and numeric for SQL Server. If the value for precision & scale is not provided, it defaults to the highest values (38, 8) and is then recognized as an ArcGIS double data type. If fields are added via the Fields designer in ArcGIS Pro, a float cannot have a precision greater than 6, and a double cannot be created with a precision less than 7.
Étapes pour reproduire
ID de bogue: BUG-000159745
Logiciel: