Commit Graph

10 Commits

Author SHA1 Message Date
Yuri Astrakhan
6457419e0d NOOP: Format all layer's SQL code (#917)
I would like to reformat all of our SQL to have a concise coding style.
This makes it far easier to understand the code for a casual contributor,
and lets us spot errors more easily.

Most importantly, it makes it much easier to grep (search) the code because it is more likely to be in the same syntax

Some key changes:
* SQL keywords are always UPPERCASE, e.g. `SELECT WHEN AS END ...`
* types, variables, aliases, and field names (identifiers) are always lower case
* `LANGUAGE 'plpgsql'` is now `LANGUAGE plpgsql` (no quotes)
* a few minor spacing/semicolon cleanups

P.S. Per @TomPohys request, `TABLE` is spelled using upper case despite being a type for consistency with PG Docs. Same for `LANGUAGE SQL` vs `LANGUAGE plpgsql`.
2020-06-08 12:19:55 -04:00
Yuri Astrakhan
8fe9af2327 Minor trailing whitespace cleanup (#596)
Remove extra spaces in a number of files.
2019-03-29 17:15:42 -04:00
Eduard Popov
0a26d2be99 Housenumber and POI calc optimisation (#247)
Using NPoints(Centroid) = NPoints, thanks edpop
2017-05-21 21:01:31 -04:00
stirringhalo
153976735f ST_PointOnSurface instead of topoint 2017-01-17 09:03:40 -05:00
stirringhalo
cda3af9215 Change SELECT to PERFORM in function and drop triggers first 2017-01-06 20:33:43 -05:00
stirringhalo
b58d80ce44 Make housenumber rerunnable 2017-01-05 14:39:04 -05:00
stirringhalo
8b4777fd79 poi and housenumber triggers 2017-01-04 17:54:15 -05:00
stirringhalo
b97e5ad9fb Convert housenumber point conversion to function 2017-01-04 17:40:59 -05:00
ImreSamu
63cdc3362d add etldoc to layer_housenumber 2016-11-10 01:11:11 +01:00
lukasmartinelli
4c85fd787e Add layer housenumber 2016-10-25 19:16:18 +02:00