<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18828"></META></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>Nicklas,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>Well actually we wouldn't change it in a micro release.
Yes I agree changing output in the micro release is probably a no
no.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>We'd change it in a minor or major release (proably major
in this case in 2.0). As far as naming goes yes that is the basic
argument. That if we replace the function with a real one. The real
one will do "more the right thing" than the old. So in essense it would be
treated like a bug fix rather than a mere change of
behavior.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>That does bring up the question of:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>Is the right answer the one you are expecting or the one
you expect.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>(are expecting meaning the one you are used to vs. you expect
(without any prior expectations of behavior))</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>For example in SQL 1/2 => 0 (both PostgreSQL and SQL Server
and a lot of relational databases behave this way by the
way)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>But if I change the behavior to suddenly return
</FONT> <FONT color=#0000ff size=2 face=Arial>0.5 (like MySQL
does)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>Do people consider it wrong because it is no longer the
expected answer of 0, but from a mathematical point of view, it is the one you
expect.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=260591311-03112009><FONT color=#0000ff
size=2 face=Arial>Regina</FONT></SPAN></DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B>
postgis-devel-bounces@postgis.refractions.net
[mailto:postgis-devel-bounces@postgis.refractions.net] <B>On Behalf Of
</B>nicklas.aven@jordogskog.no<BR><B>Sent:</B> Tuesday, November 03, 2009 6:07
AM<BR><B>To:</B> PostGIS Development Discussion<BR><B>Subject:</B> Re:
[postgis-devel] Geom/Geog Hack Plan<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Just a question for my understanding. </DIV>
<DIV>What's the argument against a special prefix in function-name for those
functions.</DIV>
<DIV>If the argument is that we then can implement the "real" function in a
micro-release, I don't think it is a good argument.</DIV>
<DIV>Exchanging the hacked version with the real will cause a changed behavior
of the function and is probably not what users expect from a micro-release, from
the policy not to change functionality in micro-releases.</DIV>
<DIV> </DIV>
<DIV>/Nicklas</DIV>
<DIV> </DIV>
<P align=left><BR><BR>2009-11-03 Paragon Corporation wrote:<BR><BR>Paul and
Kevin,<BR>><BR>>I'm in agreement with Mark too. I suppose one or 2 of
these functions is<BR>>not going to pollute our 1.5 that
much.<BR>><BR>>So how about this as a plan:<BR>><BR>>Paul picks 1 or
2 more of these kind of functions. Note we already have<BR>>buffer -- which
is now documented. Though not sure if the documentation is<BR>>clear enough
-<BR>>http://www.postgis.org/documentation/manual-svn/ST_Buffer.html (and I
think<BR>>we need to revise our documentation template yet again -- though
I'll put<BR>>that in a separate note).<BR>><BR>>The rest of the
functions get put in a wiki page and prominently linked from<BR>>the
documentation<BR>><BR>><BR>> in geography
index<BR>>http://www.postgis.org/documentation/manual-svn/ch08.html#PostGIS_GeographyF<BR>>unctions<BR>><BR>>as
well as geography description page<BR>><BR>> for easy
access<BR>>http://www.postgis.org/documentation/manual-svn/ch04.html#PostGIS_Geography<BR>><BR>>Is
everyone okay with that
plan?<BR>><BR>>Thanks,<BR>>Regina<BR>><BR>><BR>>_______________________________________________<BR>>postgis-devel
mailing
list<BR>>postgis-devel@postgis.refractions.net<BR>>http://postgis.refractions.net/mailman/listinfo/postgis-devel<BR>><BR>></P></BODY></HTML>