https://issues.qgis.org/https://issues.qgis.org/favicon.ico2015-12-22T11:12:45ZQGIS Issue TrackingQGIS Application - Bug report #14024: DB Manager fails copying a LINESTRINGMhttps://issues.qgis.org/issues/14024?journal_id=666802015-12-22T11:12:45ZPaolo Cavallinicavallini@faunalia.it
<ul><li><strong>Resolution</strong> set to <i>up/downstream</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>It turns out to be a PostGIS issue, sending upstream</p> QGIS Application - Bug report #14024: DB Manager fails copying a LINESTRINGMhttps://issues.qgis.org/issues/14024?journal_id=667462015-12-26T03:52:59ZRegis Haubourgregis.haubourg@oslandia.com
<ul></ul><p>I Paolo, I dump and restore LINESTRINGM a lot here. Maybe you added a autocast conversion type in your postgres instance?</p> QGIS Application - Bug report #14024: DB Manager fails copying a LINESTRINGMhttps://issues.qgis.org/issues/14024?journal_id=668252015-12-28T00:14:36ZPaolo Cavallinicavallini@faunalia.it
<ul></ul><p>Not that I know of. Please check also <a class="external" href="https://lists.osgeo.org/pipermail/postgis-users/2015-December/041072.html">https://lists.osgeo.org/pipermail/postgis-users/2015-December/041072.html</a><br />I'll do more testing on the PG side.<br />Thanks for the feedback.</p>