[postgis-devel] [postgis-users] PostGIS case usages

[Nicklas Avén]

I haven't touched or looked at the Haskel code to be honest.
The real work is done by PostgreSQL as I understand.
I have used it a couple of times the last maybe 3 years, and I think it
has matured quite a lot. From a user perspective the documentation is
better now.
It had some issue some years ago with the garbage collector causing the
cpu to go wild without load.But since they fixed that it has just
worked.
What I really like is that it is an easy way to use multiple database
roles from an api. 
We have a case where we have automated the jwt token creation and from
that we can assign resources to a user through the database role.
I am not a json or geojson fan, but when there is a need it is very
nice to have a thin middle ware.When it is setup all customization and
changes of the api is done in the db, which I like :-)
And the api gets separated from the data by publishing schemas with
only views and functions in. Never the tables.
/Nicklas

On Tue, 2018-10-30 at 09:21 -0700, Paul Ramsey wrote:
> On Tue, Oct 30, 2018 at 12:34 AM Nicklas Avén <nicklas.aven at jordogsko
> g.no> wrote:
> > A simple but very powerful combination of tools I use quite a lot
> > is
> > 
> > PostgreSQL/PostGIS and postgREST (http://postgrest.org)
> 
> Any issues w/ the fact that it's written in haskell? I kind of shy
> away from things in super niche languages... how's your experience?
> 
> P
> 
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20181030/f547d765/attachment.html>