From: | Wim Bertels <wim(dot)bertels(at)khleuven(dot)be> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: CRUD plpgsql generator |
Date: | 2011-06-28 08:54:48 |
Message-ID: | 1309251288.2287.31.camel@zwerfkat |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2011-06-22 at 09:02 -0500, Merlin Moncure wrote:
> On Wed, Jun 22, 2011 at 5:40 AM, Wim Bertels <wim(dot)bertels(at)khleuven(dot)be> wrote:
> > Hallo,
> >
> > does anyone have know of a free CRUD generator
> > for generating plpgsql functions for doing CRUD operations on all the
> > tables of a database or schema or just one table or..
> >
> > cf
> > http://postgresql.1045698.n5.nabble.com/CRUD-functions-similar-to-SQL-stored-procedurs-for-postgresql-tables-td3372030.html
> > http://myleshenderson.com/index.php/2007/11/16/postgresql-insert-function-generator
>
> It wouldn't be that difficult to make one IMO, but are you sure you
> really want to do this? ISTM it's a bit of an anti-pattern. If I had
that's another question/debate
cf
http://pyrseas.wordpress.com/2011/06/13/to-mvc-or-not-to-mvc/
and many more
there are so many ways to achieve the same goal:
- it is not only the model,
but certainly the way u use it that is important
- every aproach has it pros/cons
- eg a layered approach can be handy (cf other paradigm where this works
very nice and clear: OSI (networking))
- is the question of what is fashionable (cf scala being the new python,
where most of the devs are well skilled as i isnt mainstream yet)
> to do it, I would make a plpgsql function which would generate the
> functions by querying information_schema and generating create
> function statements via 'execute'.
tnx,
i will
mvg,
Wim
>
> merlin
From | Date | Subject | |
---|---|---|---|
Next Message | fluca1978 | 2011-06-28 09:12:16 | rationale behind quotes for camel case? |
Previous Message | Asfand Qazi (Sanger Institute) | 2011-06-28 08:53:08 | Re: In a view, how do I cause fields with possible NULLs to be treated as a blank string in a replace operation? |