pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <e99re41@DoCS.UU.SE>
To: Mark Stosberg <mark@summersault.com>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Porting MySQL's DESCRIBE and ENUM features
Date: Sat, 13 Nov 1999 18:04:41 +0100 (MET)
Message-ID: <Pine.GSO.4.02A.9911131755250.606-100000@Val.DoCS.UU.SE> (raw)
In-Reply-To: <382D92C3.C621932A@summersault.com>

I would myself be interested to see how the check constraints are stored,
so I can put this into the psql \d command.

mySQL's DESCRIBE is the same as the \d command in psql (Note: psql !=
Pgsql). There is no backend-level command doing this, but you are free to
query the system catalogues similar to how psql does it.

So it seems like there is no need to do a whole lot of work here. As soon
as I get the word on the contraints, I'll implement them.

	-Peter

On Sat, 13 Nov 1999, Mark Stosberg wrote:

> 
> Hello,
> 
>   I'm helping to port some somewhere from MySQL to Postgres, and am
> looking for an equivalent to MySQL's DESCRIBE function. Do you know of
> one for Postgres?
>   Specifically, one way DESCRIBE is used in this software is to get the
> values from ENUM, where a MySQL column declaration might look like this:
> 
> ReceiveMail        ENUM ('Yes', 'No') NOT NULL DEFAULT 'Yes',
> 
>   I can get the same functionality in Postgres like this, but what can
> use to get the values back of what's being checked? Thanks!
> 
> ReceiveMail        CHAR(3) check(ReceiveMail in ('Yes', 'No')) NOT NULL
> DEFAULT 'Yes',
> 
>      -mark
>   <<-------------------------------------------------------------->>
> personal website                <    Summersault Website Design
>    http://mark.stosberg.com/     >       http://www.summersault.com/
> 
> ************
> 
> 

-- 
Peter Eisentraut                  Sernanders vaeg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden




view thread (3+ messages)  latest in thread

Message-ID: <Pine.GSO.4.02A.9911131755250.606-100000@Val.DoCS.UU.SE>
Permalink:  ../Pine.GSO.4.02A.9911131755250.606-100000@Val.DoCS.UU.SE/
Also on:    postgresql.org/message-id/Pine.GSO.4.02A.9911131755250.606-100000@Val.DoCS.UU.SE

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: e99re41@DoCS.UU.SE, mark@summersault.com
  Subject: Re: [SQL] Porting MySQL's DESCRIBE and ENUM features
  In-Reply-To: <Pine.GSO.4.02A.9911131755250.606-100000@Val.DoCS.UU.SE>
  References: <382D92C3.C621932A@summersault.com> <Pine.GSO.4.02A.9911131755250.606-100000@Val.DoCS.UU.SE>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox