<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br class=""><blockquote type="cite" class="">On Aug 5, 2017, at 10:11 AM, Even Rouault <<a href="mailto:even.rouault@spatialys.com" class="">even.rouault@spatialys.com</a>> wrote:<br class=""><br class="">The condition is name = 'TrailSegment_12' not type =<br class=""></blockquote><div class=""><br class=""></div>Doh! Thanks - I had copied in your SQL but when it didn’t work I resorted to finding more examples on the web.<div class=""><br class=""></div><div class="">The reason why your suggested SQL wasn’t working was because I wasn’t setting the database connection with <grin>:</div><div class=""><br class=""></div><div class="">.open /Volumes/bigy/National/transportation/PERMANENT/sqlite/sqlite.db</div><div class=""><br class=""></div><div class="">I was able to reconfigure the schema as you suggested, and when I re-ran the SELECT SQL command, it showed the new size:</div><div class=""><br class=""></div><div class="">sqlite> SELECT SQL FROM SQLITE_MASTER WHERE NAME = 'TrailSegment_Wyoming’;<br class=""><br class=""></div><div class=""><img apple-inline="yes" id="7D76BD72-D1D1-4B5D-A65F-5B75542E7EE9" width="819" height="77" src="cid:A1C047B0-235E-4D73-B5A4-5E457CF40CCC@netgear.com" class=""></div><div class=""><br class="">But v.patch -e still wouldn’t work. I looked at the table in the GUI and it still showed the old width of the column:</div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="1710C773-1CA8-4210-9ED1-15D96C26C06C" width="357" height="293" src="cid:71376545-850A-4643-9F26-3C24387C65FB@netgear.com" class=""><br class=""><br class="">So as far as I can tell this solution won’t work, which is a bummer. I ended up getting around the issue by copying a target table, dropping all rows then inserting rows from the mismatched table (essentially as Vincent suggested).</div><div class=""><br class=""></div><div class="">I think it would be REALLY nice if we could supply a schema when importing with v.in.ogr. Apparently it allows you to specify the columns (but not specify their data type and width?). For instance I wish something like this worked:</div><div class=""><br class=""></div><div class="">v.in.ogr columns="GNIS_ID varchar(80), NAME varchar(128), etc."</div><div class=""><br class=""></div><div class="">That way, if as long as I used the same schema for different imports, they would all be combinable without any issue.<br class=""><br class=""><br class="">Best,<br class=""><br class=""><div class="">Jeshua Lacock<br class="">Founder/Engineer<br class=""><<a href="http://3DTOPO.com" class="">3DTOPO.com</a>><br class="">GlassPrinted.com<br class=""></div><br class=""></div></body></html>