<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">That would be a good idea, and I really think it could be a blocker because it leads to dead-end when editing, and sometimes leads to data loss.
( Joeren already solved that critical issue, because postgres provider dropped rows before inserting new rows, and all was lost if a constraint error was raised)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Régis<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> 3nids [via OSGeo.org] [mailto:ml-node+s1560n5045482h2@n6.nabble.com]
<br>
<b>Envoyé :</b> mardi 9 avril 2013 14:12<br>
<b>À :</b> HAUBOURG<br>
<b>Objet :</b> Re: Postgis Multipolygon :: cannot create a feature<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Shall I fill an issue? <br>
<br>
<br>
On 04/09/2013 02:10 PM, Régis Haubourg wrote: <o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
> +1 with you Denis. This restriction also implies severe known bugs when using <br>
> merge or clip tools that creates POLYGON and not MULTIPOLYGON. <br>
> Currently, I solve this by modifying postgis constraint so that it accepts <br>
> POLYGON or MULTIPOLYGON. Bu this is a bad practice. <br>
> I would really prefer that QGIS automagically propose multipolygon (or multi <br>
> point, or multilinestring) when a multi geometry type as been declared when <br>
> loading layer. <br>
> Régis <br>
> <br>
> <br>
> <br>
> -- <br>
> View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/Postgis-Multipolygon-cannot-create-a-feature-tp5045473p5045480.html" target="_top">
http://osgeo-org.1560.x6.nabble.com/Postgis-Multipolygon-cannot-create-a-feature-tp5045473p5045480.html</a><br>
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. <br>
> _______________________________________________ <br>
> Qgis-developer mailing list <br>
> <a href="/user/SendEmail.jtp?type=node&node=5045482&i=0" target="_top">[hidden email]</a>
<br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_top">
http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________ <br>
Qgis-developer mailing list <br>
<a href="/user/SendEmail.jtp?type=node&node=5045482&i=1" target="_top">[hidden email]</a>
<br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_top">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" noshade="" style="color:#CCCCCC" align="center">
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#444444">If you reply to this email, your message will be added to the discussion below:<o:p></o:p></span></b></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#444444"><a href="http://osgeo-org.1560.x6.nabble.com/Postgis-Multipolygon-cannot-create-a-feature-tp5045473p5045482.html">http://osgeo-org.1560.x6.nabble.com/Postgis-Multipolygon-cannot-create-a-feature-tp5045473p5045482.html</a>
<o:p></o:p></span></p>
</div>
<div style="margin-top:4.8pt">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:8.5pt;font-family:"Tahoma","sans-serif";color:#666666">To unsubscribe from Postgis Multipolygon :: cannot create a feature,
<a href="http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5045473&code=cmVnaXMuaGF1Ym91cmdAZWF1LWFkb3VyLWdhcm9ubmUuZnJ8NTA0NTQ3M3w0NjAxMTYx">
click here</a>.<br>
<a href="http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml"><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">NAML</span></a>
<o:p></o:p></span></p>
</div>
</div>
</body>
</html>