On 29 May 2017 at 14:25, Mark Johnson <[email protected]> wrote: >>> What makes you think that? > Based on the implementation of the QgsSpatiaLiteProvider (which only > supports TEXT, INTEGER and DOUBLE) and the documentation of QgsField. > >>> Constructor. Constructs a new QgsField object. > * \param type Field variant type, currently supported: String / Int / > Double > * \param typeName Field type (e.g., char, varchar, text, int, serial, > double). > * Field types are usually unique to the source and are stored exactly > * as returned from the data store.
OK - that needs fixing. Can you send a PR? > and the usage of type in displayString and convertCompatible. That's fine - displayString falls back to Qt's QVariant::toString(), so it handles other data types. convertCompatible uses QVariant::convert in the same way. Nyall _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
