| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
| Cc: | peter_e(at)gmx(dot)net, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] new backslash command of psql |
| Date: | 2000-02-20 21:50:51 |
| Message-ID: | 200002202150.QAA19651@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> [spelling mistake in Subject corrected]
> > Do we have to have a \eset command? Can't we just use \set that we
> > already have?
>
> Not sure. Seems \set is for just setting a variable. To change the
> client encoding, we need to do more.
We already have some special variable meanings like \set PROMPT1 which
controls the psql prompt. Seems an encoding variable can be made too.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Bitmead | 2000-02-20 23:10:08 | Re: [HACKERS] psql and Control-C |
| Previous Message | Tom Lane | 2000-02-20 17:41:44 | Re: [HACKERS] Re: SQL compliance - why -- comments only at psql level? |