| From: | Marc Evans <Marc(at)SoftwareHackery(dot)Com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Odd behavior observed |
| Date: | 2006-09-19 17:13:11 |
| Message-ID: | 20060919131207.U27583@me.softwarehackery.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, 19 Sep 2006, Tom Lane wrote:
> Marc Evans <Marc(at)SoftwareHackery(dot)Com> writes:
>> ... I have a table with about 15000 records in it, which I
>> would like to add a new column to. The alter command shows success.
>> However, testing inserts reveals that the data for the new column is never
>> stored.
>
> What do you mean by that exactly? The example you showed seems to be
> doing just what it's supposed to.
In the failure mode, the source_record column always has the value NULL,
regardless of any value specified in an insert. If I use UPDATE to change
a record, the value is properly stored.
- Marc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-19 17:15:48 | Re: Odd behavior observed |
| Previous Message | Tom Lane | 2006-09-19 17:10:40 | Re: Odd behavior observed |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-19 17:15:48 | Re: Odd behavior observed |
| Previous Message | Tom Lane | 2006-09-19 17:10:40 | Re: Odd behavior observed |