<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hi Daniel, there are <tt class="gmail-LITERAL">INOUT</tt> parameters in postgres</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">But then using them will give the columns a strange ordering</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">like having the `seq` column in the second or third column.<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Oct 24, 2018 at 8:55 PM Daniel Kastl <<a href="mailto:daniel@georepublic.de">daniel@georepublic.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Vicky,<div><br></div><div>I agree with your proposal.</div><div><br></div><div>There is maybe one point, which we would loose, when we remove the names on compulsory parameter: code readability.</div><div><br></div><div>Take your example:</div><div><a href="https://github.com/pgRouting/admin/wiki/RFC3#developers-steps-to-take" target="_blank">https://github.com/pgRouting/admin/wiki/RFC3#developers-steps-to-take</a><br></div><div><br></div><div>Now it's not so easy anymore to understand the first three input parameters, so I would suggest to somehow encourage developers (or make it a required formal rule) to append the parameter name in each line as a comment.</div><div><br></div><div><div><font face="monospace, monospace">CREATE OR REPLACE FUNCTION pgr_aStarCost(</font></div><div><font face="monospace, monospace"> ---------------- remove the names on compulsory parameters</font></div><div><font face="monospace, monospace"> TEXT, # edges_sql (required)</font></div><div><font face="monospace, monospace"> BIGINT, # </font><span style="background-color:initial;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;color:rgb(36,41,46)">start_vid</span><span style="font-family:monospace,monospace"> </span><span style="font-family:monospace,monospace">(required)</span></div><div><font face="monospace, monospace"> BIGINT, # </font><span style="background-color:initial;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;color:rgb(36,41,46)">end_vid</span><span style="font-family:monospace,monospace"> </span><span style="font-family:monospace,monospace">(required)</span></div><div><font face="monospace, monospace"> directed BOOLEAN DEFAULT true,</font></div></div><div><font face="monospace, monospace"> ...</font></div><div><br></div><div>I understand, that PostgreSQL does not allow us to use the same attribute name twice for in IN and OUT parameters, if we want to use named parameters. But isn't this something that could be solved in future versions of PostgreSQL? Looks more like a bug than a feature, because why would someone want to use the parameter name of one, that is defined as "OUT"?</div><div><br></div><div>Best regards,</div><div>Daniel</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 25, 2018 at 3:44 AM Vicky Vergara <<a href="mailto:vicky@georepublic.de" target="_blank">vicky@georepublic.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Dear Users and developers</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">We would like to hear your feedback about:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"> Positional and named parameters on pgRouting functions</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">That is described here:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/pgRouting/admin/wiki/RFC3" target="_blank">https://github.com/pgRouting/admin/wiki/RFC3</a></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">The aim is to enforce positional notation on compulsory parameters and allow named notation on optional parameters</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">That enforcement would take place on version 3.0.0 scheduled to be released on September 2019.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">We will appreciate your feedback.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Regards</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">The pgRouting team</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br clear="all"></div><br>-- <br><div dir="ltr" class="m_4032743169840698737m_4680520200487212110gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre>Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany
Vicky Vergara
Operations Research
eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a>
Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a>
Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9
Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
<span></span></pre></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/pgrouting-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/pgrouting-users</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_4032743169840698737gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse">Georepublic UG & Georepublic Japan<br>eMail: <a href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66,99,171)" target="_blank">daniel.kastl@georepublic.de</a><br>Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a></span><div><br></div><div><br></div><div><br></div></div></div></div></div>
_______________________________________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/pgrouting-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre>Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany
Vicky Vergara
Operations Research
eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a>
Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a>
Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9
Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
<span></span></pre></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>