Re: Implementing "thick"/"fat" databases - Mailing list pgsql-general

From David Johnston
Subject Re: Implementing "thick"/"fat" databases
Date
Msg-id 4769A6F9-BB60-4D88-A5F7-8897656FC755@yahoo.com
Whole thread Raw
In response to Re: Implementing "thick"/"fat" databases  (Chris Travers <chris.travers@gmail.com>)
Responses Re: Implementing "thick"/"fat" databases  (Chris Travers <chris.travers@gmail.com>)
List pgsql-general
>
> Now for the application, you can create an API that is semantically
> clearer.  But PostgreSQL doesn't provide an easy way of calling
> procedures of this sort out of select/update/insert statements and
> select is the only way to do this.
>
>

A semantically accurate way to run "procedures" is:

DO $$ BEGIN PERFORM function(); END $$;

It would be nice if you could use PERFORM outside of plpgsql...

Now, this is not standard SQL but it does convey the desired semantics.  That said, proper function naming can convey
similarsemantic information as well. 

David J.



pgsql-general by date:

Previous
From: David Johnston
Date:
Subject: Re: Implementing "thick"/"fat" databases
Next
From: Adrian Klaver
Date:
Subject: Re: weird table sizes