| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vivek Khera <khera(at)kcilink(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] schema error upgrading from 7.1 to 7.2 |
| Date: | 2002-02-20 23:18:13 |
| Message-ID: | 3304.1014247093@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-general |
Vivek Khera <khera(at)kcilink(dot)com> writes:
> Then how come pg_dump outputs it that way? Is it because that's how I
> did it when creating the schema in the first place?
Presumably.
> TL> Because it is not one: it is a datatype behavioral change.
> It isn't documented in the HISTORY file in any way shape or form.
HISTORY says, under "Migration to version 7.2":
* The date/time value 'current' is no longer available. You will need to
rewrite your applications.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-20 23:21:41 | Re: Dates and year 2000 |
| Previous Message | Vivek Khera | 2002-02-20 21:41:51 | Re: [GENERAL] schema error upgrading from 7.1 to 7.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Wood | 2002-02-20 23:37:41 | Re: returning rows from a function |
| Previous Message | David Blood | 2002-02-20 23:08:27 | query optimization Anyone know a better way to run this query |