|
Home > Archive > Pgadmin > February 2006 > Error when trying to add DEFAULT Value to NEW column
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error when trying to add DEFAULT Value to NEW column
|
|
| Leon du Plessis 2006-02-02, 9:28 am |
| Hi,
If this is a known issue, please ignore. just direct me to the fix:
Receiving an error "Column 'no' does not exist" when trying to add a default
value to a new column via properties panel.
When you create the new column without a default value, it's fine. The
default value can then be added afterwards.
Also subsequent deletion and re-creation of the column does not produce the
same condition and the default value can then be added with no further
problems.
The error indicates the column "no" does not exist, but I am trying to add
straight text to the default value. Can't see why that field is trying to
link/check columns. I have tried quotes.
Using Version 8.1 on Windows XP SP2 and pgadmin 1.4.1.
Thank you, kindly
L.
| |
| Leon du Plessis 2006-02-02, 9:28 am |
| Ok, This was me. When I looked at the SQL statement to trace problem, I
(sheepishly) used the wrong quotes !
Can the single quotes be added automatically if they are not supplied?
-----Original Message-----
From: pgadmin-support-owner@postgresql.org
[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Leon du Plessis
Sent: 02 February 2006 03:38 PM
To: pgadmin-support@postgresql.org
Subject: [pgadmin-support] Error when trying to add DEFAULT Value to NEW
column
Hi,
If this is a known issue, please ignore. just direct me to the fix:
Receiving an error "Column 'no' does not exist" when trying to add a default
value to a new column via properties panel.
When you create the new column without a default value, it's fine. The
default value can then be added afterwards.
Also subsequent deletion and re-creation of the column does not produce the
same condition and the default value can then be added with no further
problems.
The error indicates the column "no" does not exist, but I am trying to add
straight text to the default value. Can't see why that field is trying to
link/check columns. I have tried quotes.
Using Version 8.1 on Windows XP SP2 and pgadmin 1.4.1.
Thank you, kindly
L.
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.23/243 - Release Date: 2006/01/27
| |
| Dave Page 2006-02-02, 9:28 am |
|
____________________
____________
From: pgadmin-support-owner@postgresql.org
[mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Leon du
Plessis
Sent: 02 February 2006 14:49
To: pgadmin-support@postgresql.org
Subject: Re: [pgadmin-support] Error when trying to add DEFAULT
Value to NEW column
Ok, This was me. When I looked at the SQL statement to trace
problem, I (sheepishly) used the wrong quotes !
Oh good - I was scratching my head trying to track that one down!
Can the single quotes be added automatically if they are not
supplied?
Not really, because it's difficult to know if they are required or not,
especially if custom datatypes are used, or the default is actually an
expression.
Regards,. Dave.
|
|
|
|
|