Re: Table/Column Constraints

From: Rod Taylor <rbt(at)zort(dot)on(dot)ca>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Table/Column Constraints
Date: 2000-11-21 05:22:05
Message-ID: 3A1A067D.A9156446@zort.on.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christopher Kings-Lynne wrote:
>
> > I like this conversation as not a day goes by where I don't wish I could
> > edit the dump of a database rather than keeping structure entirely
> > seperate -- and actually do so in a useful manner. That said, whats the
> > possibility of maintaining comments if the SQL dumps actually became
> > humanly editable?
>
> >From reading the pg_dump source code, pg_dump creates a set of 'COMMENT ON
> ...' statements that should recreate all the comments associated with an
> oid. So - there shouldn't be a problem, should there?

I was thinking of SQL that looks something like:

/*******************************
* TABLE: example
*
* Used to accomplish stuff
*/
CREATE TABLE example
( example_id serial

/* Must be a ZIP or Postal Code */
, region varchar(6) UNIQUE
NOT NULL

/* Descriptive text */
, description varchar(60) NOT NULL
);

I've always made the assumption that anything in the /* */ was dropped.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2000-11-21 05:40:22 Re: SET SESSION CHARACTERISTICS
Previous Message The Hermit Hacker 2000-11-21 05:20:49 Re: [HACKERS] Re: PHPBuilder article -- Postgres vs MySQL