Update exception_safe.md

User's and orgs are not part of the client interface, removed those parameters.
This commit is contained in:
Rafa de la Torre 2017-05-23 13:01:18 +02:00 committed by GitHub
parent d7fad6d8d3
commit 97961a02df

View File

@ -18,7 +18,7 @@ These functions are useful in cases when it is undesirable to rollback a transac
Fo example if a table is geocoded with: Fo example if a table is geocoded with:
```sql ```sql
UPDATE table SET the_geom=cdb_geocode_street_point(user,NULL,address,city,NULL,country); UPDATE table SET the_geom=cdb_geocode_street_point(address,city,NULL,country);
``` ```
In case of the user geocoding quota being exhausted mid-process, the user could In case of the user geocoding quota being exhausted mid-process, the user could
@ -28,7 +28,7 @@ transaction rollback.
We can avoid the problem using the corresponding exception-safe function: We can avoid the problem using the corresponding exception-safe function:
```sql ```sql
UPDATE table SET the_geom=_cdb_geocode_street_point_exception_safe(user,NULL,address,city,NULL,country); UPDATE table SET the_geom=_cdb_geocode_street_point_exception_safe(address,city,NULL,country);
``` ```
# Addition Information # Addition Information