Name your routines

Whenever possible, use generally accepted names for routines by using your new data types.

For example, the Overlaps() routine in the SimpleMap DataBlade® module does precisely what its name indicates. Users know what to expect when they call it.

Because your database server supports polymorphism, it is possible that another routine of the same name exists in the system. If you are concerned that your routine provides a different service or has the same signature as another, similarly named routine from another DataBlade module (that is, none of the arguments of your routine are of a data type defined in your DataBlade module), consider renaming the routine or qualifying its name with a three-character DataBlade module prefix such as USR. Doing so helps avoid conflicts in the system and confusion among your users.

Assume, for example, that you are creating the OtherMap DataBlade module with a routine named Overlaps() that provides a different service than the Overlaps() routine supplied by the SimpleMap DataBlade module. In addition, your Overlaps() routine takes polygon data types not defined in the OtherMap DataBlade module. If the three-character prefix of your DataBlade module is OTH, then you might define your routine as follows: 
OthOverlaps(Polygon, Polygon)
However, if your Overlaps() routine takes arguments of data types defined in the OtherMap DataBlade module, you might define Overlaps() as follows: 
Overlaps(OthPolygon, OthPolygon)