[postgis-devel] About the ST_ prefix

[Obe, Regina]

Someone else mentioned this. Yes part of me wishes it wasn't so.

The thinking (who's thinking was this?  Maybe Paul) was that it would be
easier if people didn't have to 
worry about putting ST_ or not putting ST_ in front of functions.  also
the functions appear nicely together to compensate for the fact that
we didn't put the functions in a schema.

Having now worked with SQL Server 2008 a bit.  They don't put ST in
front of functions that are obviously not OGC compliant and are their
own creation.  
I suspect other spatial databases follow that convention -- of using a
different prefix for their custom things or no prefix at all.

To compensate for this compromise - that may lead people to believe taht
all ST_s are compliant, that is why we have this section

http://postgis.refractions.net/documentation/manual-svn/ch08.html#id2665
244

So people who only want to use compliant functions can look at that list
and only use those.



-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of strk
Sent: Friday, January 09, 2009 8:58 AM
To: postgis-devel at postgis.refractions.net
Subject: [postgis-devel] About the ST_ prefix

I noticed you're switching a lot postgis functions to
start with the ST_ prefix, no matter wheter they are
or not defined by ISO/SQLMM.

What's the rationale behind that ?

If I'm not wrong the OGC standard had its own naming
for the same functions, and I tought it was planned
for postgis to keep the no-prefix
functions as primary and add the compliant-version on
top ?

--strk;

 GIS & Flash consultant/developer           ()  ASCII Ribbon Campaign
 http://foo.keybit.net/~strk/services.html  /\  Keep it simple! 
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.