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

From Bill Moran
Subject Re: Preserving the source code of views
Date
Msg-id 20131020080121.b3e98cc80146e33ec3b8ae64@potentialtech.com
Whole thread Raw
In response to Preserving the source code of views  (Brian Crowell <brian@fluggo.com>)
Responses Re: Preserving the source code of views
List pgsql-general
On Sat, 19 Oct 2013 22:38:28 -0500 Brian Crowell <brian@fluggo.com> wrote:

> Hello! I'm evaluating PostgreSQL as a replacement for SQL Server in our
> in-house systems. I've been really impressed with it so far, and I'm eager
> to try it with our data sets.
>
> I've run across one thing that would make a transfer difficult. Postgres
> doesn't preserve the source code for views, as far as I can tell. It parses
> them and then prints them its own way. We have a lot of complicated views,
> where both the formatting and the comments are significant. In fact, we
> produce some of our system documentation directly from the comments.
>
> Is there currently a way to preserve the original source code of a view as
> entered in the CREATE VIEW statement?

You could adjust your workflow to use something like dbsteward:
http://dbsteward.org/

--
Bill Moran <wmoran@potentialtech.com>


pgsql-general by date:

Previous
From: "Huang, Suya"
Date:
Subject: Re: [ADMIN] what's the efficient/safest way to convert database character set ?
Next
From: John R Pierce
Date:
Subject: Re: [ADMIN] what's the efficient/safest way to convert database character set ?