<p dir="ltr">About view.<br /> I found where I saw it was a discussion solve some problems with view <a
href="https://wiki.postgresql.org/wiki/Todo#Views_and_Rules">https://wiki.postgresql.org/wiki/Todo#Views_and_Rules</a>,
ieit is in the list of TODO, so there is a chance that it will be implemented. <div class="gmail_quote">03 Май 2015 г.
12:15пользователь "Sergey Grinko" <<a href="mailto:sergey.grinko@gmail.com">sergey.grinko@gmail.com</a>>
написал:<brtype="attribution" /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><pdir="ltr">Thank you Jim!<br /> Views, they also have the problem. In my practice I use them
verylittle, so do not just remember them.<br /> Somewhere I read that already are going to introduce their storage
source.<br/> If I find this source, then I write the link here.<br /> I am a supporter of conservation of the source
code.<br/> I hope that the PostgreSQL developers still implement the storage of the full DDL and PostgreSQL then
receiveanother plus in competition with commercial databases. <div class="gmail_quote">01 Май 2015 г. 23:03
пользователь"Jim Nasby" <<a href="mailto:Jim.Nasby@bluetreble.com" target="_blank">Jim.Nasby@bluetreble.com</a>>
написал:<brtype="attribution" /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">On4/30/15 6:44 AM, Sergey Grinko wrote:<br /><blockquote class="gmail_quote" style="margin:0 0
0.8ex;border-left:1px #ccc solid;padding-left:1ex"> Now create a script in the application of its function parameters
and<br/> return values can be declared using %TYPE.<br /> However, when you save the script is stored inside the server
onlywhat<br /> is considered his body. Thus, we obtain:<br /></blockquote> ...<br /><br /> We actually mung things a
lotworse when it comes to views, so I'm curious why you're only worried about the problems with stored functions?<br
/><br/> FWIW, I think the best 'solution' to this right now is to actually keep your original definitions as files in
yourVCS 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.<br/><br /> That's still not terribly satisfying since unlike other forms of software you now have all that
definitionboth in your VCS and the database itself, but ISTM that's a much bigger problem than the small amount of info
welose from stored functions...<br /> -- <br /> Jim Nasby, Data Architect, Blue Treble Consulting<br /> Data in
Trouble?Get it in Treble! <a href="http://BlueTreble.com" target="_blank">http://BlueTreble.com</a><br
/></blockquote></div></blockquote></div>