| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: AW: AW: Truncation of char, varchar types |
| Date: | 2001-04-12 12:43:50 |
| Message-ID: | 3AD5A306.3D13926A@alumni.caltech.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Someone said Oracle raises an error.
> > Informix seems to be the only other db that truncates silently.
> Raises a warning instead of error. Would need to check Sybase and DB2, but ...
> Yes, good. Do we want this in 7.1.0 ? Seems, yes :-(
No, pretty sure this will not fly for the 7.1.x cycle, no matter what we
end up deciding is the best approach (with SQL9x getting more votes than
most other proposals, but The Right Thing having the most votes of all
;)
We are at the tail end of the beta cycle, and a change in behavior which
is this fundamental needs more time and discussion. All imho of
course...
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-04-12 15:47:40 | Re: age() function documentation |
| Previous Message | Zeugswetter Andreas SB | 2001-04-12 08:24:01 | AW: AW: AW: Truncation of char, varchar types |