On Sat, Mar 30, 2019, 21:55 Anita Graser <[email protected]> wrote: > Hi, > > I have a CSV with multiple columns including some WKT columns containing > polygon definitions. I've exported the layer as GeoPackage. Later, I wanted > to import the GeoPackage content to PostGIS but the import fails because > the WKT strings are longer than the fields DB Manager creates. The layer > properties state that the WKT columns are text(255) but the strings are > considerably longer. > > (If I directly import the CSV to PostGIS, all is well.) > > I'm not sure what kind of ticket I should open ... > - Option #1: DB Manager should be more fault tolerant and create less > restrictive columns > - Option #2: QGIS shouldn't create GeoPackages that store long strings in > field defined as text(255) > > What do you recommend? >
Hi Anita, I think 2 looks like a bug. I didn't look at it but from your description seems like DB manager correctly follows the (wrong) information from the provider. > Regards, > Anita > > > _______________________________________________ > 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
_______________________________________________ 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
