Re: Preserving the source code of views - Mailing list pgsql-general

From Brian Crowell
Subject Re: Preserving the source code of views
Date
Msg-id CAAQkdDo0O1V5+cKQuNDzuQ1vFmwR5SFYRFmSwPsL-0TaNdUZhQ@mail.gmail.com
Whole thread Raw
In response to Re: Preserving the source code of views  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Preserving the source code of views  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
On Sat, Oct 19, 2013 at 11:37 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> For my work is very significant @a point - I wrote and I am writing usually
> database centric stored procedures centric applications and @a works
> perfect. For me a SQL code is code as any other - I use a my favourite
> editor, I use a GIT for versioning, I can simple distributed application to
> my customers.

What do you do to manage dependencies among the objects? How do you
have your scripts set up to handle deploying, say, an extra column to
an existing view?

Our databases tended to be SP-heavy before I came along. I'm big on
views because that allows my client code to do very specific queries
without having to write new SPs all the time.

--Brian


pgsql-general by date:

Previous
From: Brian Crowell
Date:
Subject: Re: Preserving the source code of views
Next
From: Pavel Stehule
Date:
Subject: Re: Preserving the source code of views