| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-sql(at)hub(dot)org |
| Subject: | Re: [SQL] char type seems the same as char(1) |
| Date: | 1998-12-14 03:56:29 |
| Message-ID: | 199812140356.WAA06630@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> > > > If we use char1 for internal tables, we should allow it
> > > > externally, if only as char1. I will add it to the TODO list.
> > > As what?
> > As "char1", of course.
>
> Oh well. Thought that there might be other solutions, that's all...
Well, since ansi wants char to be char(1) and to be like that other
char's, I don't think we have a choice but to choose another name.
--
Bruce Momjian | http://www.op.net/~candle
maillist(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 | Vladimir Dobrokhotov | 1998-12-14 07:14:53 | binary search |
| Previous Message | Jayvee Vibar | 1998-12-14 02:45:13 | JDBC for postgreSQL?? |