https://issues.qgis.org/https://issues.qgis.org/favicon.ico2014-03-03T23:26:59ZQGIS Issue TrackingQGIS Application - Feature request #9689: Joins should be more mindful of DBF field name length limitationshttps://issues.qgis.org/issues/9689?journal_id=493582014-03-03T23:26:59ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Category</strong> set to <i>Vectors</i></li><li><strong>Target version</strong> changed from <i>Version 2.2</i> to <i>Future Release - Nice to have</i></li><li><strong>Operating System</strong> deleted (<del><i>Windows 7 x64</i></del>)</li></ul><p>Not an easy task, the prefix is necessary to avoid attributes with the same name, then shapefiles have a 10 chars column name limit. Of course the vector with the joined table can be exported to a more advanced format, like spatialite or postgis where such limitation does not exist.</p>
<p>How do you suggest to solve the issue with shapefiles?</p> QGIS Application - Feature request #9689: Joins should be more mindful of DBF field name length limitationshttps://issues.qgis.org/issues/9689?journal_id=493932014-03-04T06:13:26ZEmilio G1@emil.io
<ul></ul><p>The software should simply check if the name is a duplicate. If not, leave it as is. It cannot simply prepend the layer name and hope that this is not a duplicate, so it must be doing some level of checking now, no?</p> QGIS Application - Feature request #9689: Joins should be more mindful of DBF field name length limitationshttps://issues.qgis.org/issues/9689?journal_id=493942014-03-04T06:56:33ZJürgen Fischerjef@norbit.de
<ul></ul><p>Emilio G wrote:</p>
<blockquote>
<p>The software should simply check if the name is a duplicate. If not, leave it as is. It cannot simply prepend the layer name and hope that this is not a duplicate, so it must be doing some level of checking now, no?</p>
</blockquote>
<p>It doesn't. There is no restriction before you decide that you want to save the data in a shapefile. And the mapping of arbitrary field names to attributes in shapefiles handled (although it's not as nice as going without a prefix, if that's not necessary for unique field names).</p>
<p>Not sure, if it isn't a bug in the table manager plugin, that it shows joined fields on a shapefile. I believe it wouldn't work with those, even if the names were 11 characters or less.</p> QGIS Application - Feature request #9689: Joins should be more mindful of DBF field name length limitationshttps://issues.qgis.org/issues/9689?journal_id=494122014-03-04T23:42:38ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Emilio G wrote:</p>
<blockquote>
<p>The software should simply check if the name is a duplicate. If not, leave it as is. It cannot simply prepend the layer name and hope that this is not a duplicate, so it must be doing some level of checking now, no?</p>
</blockquote>
<p>how other software does?</p> QGIS Application - Feature request #9689: Joins should be more mindful of DBF field name length limitationshttps://issues.qgis.org/issues/9689?journal_id=505372014-05-02T14:03:49ZAntonio Locandroantonio.locandro@cocesna.org
<ul></ul><p>When you open the attribute table it shows the join fields as they are unless duplicate I believe it adds a _1 or something to distinguish</p>
<p>Now when doing a Query it adds the layer name + "." + Field to be able to make a difference of one to another</p>
<p>This helps when you save a layer with a join, since the attribute table have the same column names as the join fields if possible</p> QGIS Application - Feature request #9689: Joins should be more mindful of DBF field name length limitationshttps://issues.qgis.org/issues/9689?journal_id=708402016-06-13T16:36:36ZNyall Dawson
<ul><li><strong>Resolution</strong> set to <i>fixed/implemented</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>QGIS supports custom prefixes for joined layers, so this should be fixed now</p>