Re: Preserving the source code of views

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: Brian Crowell <brian(at)fluggo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Preserving the source code of views
Date: 2013-10-20 12:01:21
Message-ID: 20131020080121.b3e98cc80146e33ec3b8ae64@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, 19 Oct 2013 22:38:28 -0500 Brian Crowell <brian(at)fluggo(dot)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(at)potentialtech(dot)com>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2013-10-20 19:22:07 Re: [ADMIN] what's the efficient/safest way to convert database character set ?
Previous Message Huang, Suya 2013-10-20 10:56:17 Re: [ADMIN] what's the efficient/safest way to convert database character set ?