Re: Stored procedure workflow question - Mailing list pgsql-general

From Rob Sargent
Subject Re: Stored procedure workflow question
Date
Msg-id 5488F058.908@gmail.com
Whole thread Raw
In response to Stored procedure workflow question  (Israel Brewster <israel@ravnalaska.net>)
List pgsql-general
On 12/10/2014 05:53 PM, Israel Brewster wrote:
Currently, when I need to create/edit a stored procedure in Postgresql, my workflow goes like the following:

- Create/edit the desired function in my "DB Commands" text file
- Copy and paste function into my development database
- Test
- repeat above until it works as desired
- Copy and paste function into my production DB.

To edit an existing function, the workflow is basically the same as above, but I first have to find the function in my file.

This whole workflow just feels kludgy to me. Is there a better way? Or is that essentially the recommended procedure? Thanks.
-----------------------------------------------
Israel Brewster
Systems Analyst II
Ravn Alaska
5245 Airport Industrial Rd
Fairbanks, AK 99709
(907) 450-7293
-----------------------------------------------





I don't quite follow "cut and paste it into <some> database", but you method doesn't sound any more kludy than code-compile-test-install workflow in other coding environments. I will say emacs make this a snap, but I won't say how;)

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Stored procedure workflow question
Next
From: Guyren Howe
Date:
Subject: Re: service allowing arbitrary relations was Re: hstore, but with fast range comparisons?