Re: Implementing "thick"/"fat" databases

From: David Johnston <polobo(at)yahoo(dot)com>
To: Chris Travers <chris(dot)travers(at)gmail(dot)com>
Cc: Karl Nack <karlnack(at)futurityinc(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Implementing "thick"/"fat" databases
Date: 2011-07-23 20:32:59
Message-ID: 4769A6F9-BB60-4D88-A5F7-8897656FC755@yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 similar semantic information as well.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2011-07-23 20:36:44 Re: weird table sizes
Previous Message David Johnston 2011-07-23 20:10:59 Re: Implementing "thick"/"fat" databases