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

From Brian Crowell
Subject Preserving the source code of views
Date
Msg-id CAAQkdDod-N6nPbCKZ12zxjmYND=8tak3cZyJN40hELEbEfcw0A@mail.gmail.com
Whole thread Raw
Responses Re: Preserving the source code of views  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
Re: Preserving the source code of views  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: Preserving the source code of views  (Bill Moran <wmoran@potentialtech.com>)
Re: Preserving the source code of views  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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?

--Brian

pgsql-general by date:

Previous
From: whiplash
Date:
Subject: Cast user defined type to composite type
Next
From: Gavin Flower
Date:
Subject: Re: Preserving the source code of views