| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Casting, again |
| Date: | 2000-05-15 14:53:08 |
| Message-ID: | 200005151453.KAA17353@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> For 7.0, I changed the implementation to decouple string types and
> other types by natively supporting char_length() (and
> character_length()), the SQL92-defined length function(s) for strings.
> I left length() for the other types.
>
> I believe that this is mentioned in the release notes.
>
> btw, what were we hoping to accomplish with length(755)? Why isn't "3"
> a good answer??
Three is the right answer. I was just wondering why it used to fail,
but now it works.
--
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 | Benjamin Adida | 2000-05-15 15:12:48 | Re: Proposal: replace no-overwrite with Berkeley DB |
| Previous Message | Tom Lane | 2000-05-15 14:52:33 | Re: type conversion discussion |