Re: Preserving the source code of views

From: Brian Crowell <brian(at)fluggo(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Preserving the source code of views
Date: 2013-10-21 02:45:16
Message-ID: CAAQkdDo0O1V5+cKQuNDzuQ1vFmwR5SFYRFmSwPsL-0TaNdUZhQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Oct 19, 2013 at 11:37 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2013-10-21 04:39:23 Re: Preserving the source code of views
Previous Message Brian Crowell 2013-10-21 02:38:59 Re: Preserving the source code of views