improve table dumping

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: improve table dumping
Date: 2003-02-28 07:58:56
Message-ID: 079f01c2deff$3eb9dcb0$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Hi,

This implements a new layout for psql's \d command and actually shows rule
definitions as well as names:

Indexes:
"users_users_pkey" PRIMARY KEY btree (userid),
"users_users_username_key" UNIQUE btree (username),
"users_users_email_lower_idx" btree (lower(email)),
Foreign Key Constraints:
"$1" FOREIGN KEY (referrer) REFERENCES users_users(userid) ON UPDATE NO
ACTION ON DELETE SET NULL
Rules:
"test_rule" AS ON INSERT TO users_users DO INSTEAD NOTHING;
Triggers:
"RI_ConstraintTrigger_1105134",
"RI_ConstraintTrigger_1105135",
"RI_ConstraintTrigger_1105138",
"RI_ConstraintTrigger_1105139",
"RI_ConstraintTrigger_1105396",
"RI_ConstraintTrigger_1105397"

I think it's an improvement - it make a lot more stuff just fit on the
screen, and is a lot easier to read! I did also notice that pg_get_ruledef
appends a semicolon, whereas the other pg_get_* functions do not...

Chris

Attachment Content-Type Size
describe.txt text/plain 7.2 KB

Browse pgsql-patches by date

  From Date Subject
Next Message greg 2003-02-28 15:00:47 Re: XML ouput for psql
Previous Message Rod Taylor 2003-02-28 03:28:44 psql re-work