Changes between Initial Version and Version 1 of Ticket #3920


Ignore:
Timestamp:
Jan 20, 2011, 12:43:33 AM (13 years ago)
Author:
KK
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3920

    • Property Keywords numeric added; numeroc removed

  • Ticket #3920 – Description

    initial v1  
    11Hello,
    22
    3 if OGR creates a new SQLServer table, it derives SQLServer datatypes from dbase datatypes. For numeric columns, it chooses either NUMERIC(x, 0) or NUMERIC(x,y). In practise, depending on the different kinds of shapefile, this can lead to an numeric overflow indicated by the SQLServer driver. In many cases, OGR creates the target table and crashes while inserting the first row.
     3if OGR creates a new SQLServer table, it derives SQLServer datatypes from dbase datatypes. For numeric columns, it chooses either NUMERIC(x, 0) or NUMERIC(x,y). In practise, depending on the different kinds of shapefiles, this can lead to a numeric overflow indicated by the SQLServer driver. In many cases, OGR creates the target table and crashes while inserting the first row.
    44
    5 It would be better, to choose INT or FLOAT as default numeric datatypes. If anybody prefers NUMERIC(), he could create the target table before starting OGR and runs OGR in -append mode.
     5A good solution would be if OGR chooses INT instead of NUMERIC(x,0) and FLOAT instead of NUMERIC(x,y). If anybody prefers NUMERIC() datatypes, he can create the target table before starting OGR and runs OGR in -append mode.
    66
    77Kind Regards,
    88
    9 Klaus
     9Klaus Kuehne
     10
     11Leibniz Institute for Applied Geophysics
     12
     13Hannover, Germany