From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Sergey Grinko <sergey(dot)grinko(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Loss of some parts of the function definition |
Date: | 2015-05-01 21:02:55 |
Message-ID: | 5543E9FF.4060501@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/30/15 6:44 AM, Sergey Grinko wrote:
> Now create a script in the application of its function parameters and
> return values can be declared using %TYPE.
> However, when you save the script is stored inside the server only what
> is considered his body. Thus, we obtain:
...
We actually mung things a lot worse when it comes to views, so I'm
curious why you're only worried about the problems with stored functions?
FWIW, I think the best 'solution' to this right now is to actually keep
your original definitions as files in your VCS and use something like
sqitch for deployment. Taken to it's logical extreme, that means that
the only thing you ever 'patch' is an actual table (via ALTER TABLE), or
indexes. Everything else essentially gets treated like regular code.
That's still not terribly satisfying since unlike other forms of
software you now have all that definition both in your VCS and the
database itself, but ISTM that's a much bigger problem than the small
amount of info we lose from stored functions...
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2015-05-01 21:07:06 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
Previous Message | Jim Nasby | 2015-05-01 20:53:30 | Re: CTE optimization fence on the todo list? |