Skip site navigation (1) Skip section navigation (2)

Re: [NOVICE] Problem with inserting: attribute 'extended_reason'

From: "Joel Burton" <joel(at)joelburton(dot)com>
To: "Wim" <wdh(at)belbone(dot)be>, <pgsql-novice(at)postgresql(dot)org>,<pgsql-general(at)postgresql(dot)org>
Subject: Re: [NOVICE] Problem with inserting: attribute 'extended_reason'
Date: 2002-05-21 13:38:38
Message-ID: JGEPJNMCKODMDHGOBKDNCEOKCOAA.joel@joelburton.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-novice
> -----Original Message-----
> From: pgsql-novice-owner(at)postgresql(dot)org
> [mailto:pgsql-novice-owner(at)postgresql(dot)org]On Behalf Of Wim
> Sent: Tuesday, May 21, 2002 9:17 AM
> To: pgsql-novice(at)postgresql(dot)org; pgsql-general(at)postgresql(dot)org
> Subject: [NOVICE] Problem with inserting: attribute 'extended_reason'
>
>
> Hi all,
>
>
> In a perl script I try to insert a row with the follow SQL command:
>
> DBD::Pg::st execute failed: ERROR:  Relation 'billing' does not have
> attribute 'extended_reason' at ./upd_billing.pl line 147, <BILLINGFILE>
> line 241.
>
> Does anyone of you knows what this means?

Table "billing" does not have field "extended_reason".

In psql, use "\d billing" to see a list of fields in the table. Perhaps you
called it something else.

- J.

Joel BURTON | joel(at)joelburton(dot)com | joelburton.com | aim: wjoelburton
Knowledge Management & Technology Consultant


In response to

pgsql-novice by date

Next:From: Ron JohnsonDate: 2002-05-21 20:20:13
Subject: Large tables being split at 1GB boundary
Previous:From: WimDate: 2002-05-21 13:16:44
Subject: Problem with inserting: attribute 'extended_reason'

pgsql-general by date

Next:From: Andrew SullivanDate: 2002-05-21 14:13:56
Subject: Re: monitoring running transaction
Previous:From: Oliver ElphickDate: 2002-05-21 13:31:18
Subject: Re: want basic help with C

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group