You forgot to mention that all the functions/views that utilized that table also now point to the
original table with the changed name, because it doesn't store the table name, it stores the table oid.
Berend Tober wrote:
A. Kretschmer wrote:
am Wed, dem 13.09.2006, um 15:46:58 -0700 mailte
Thanks for all of your help. I backed up the table and used the PgAdmin
tool to create Insert statements. It did it in two sets. I reran the
first set and it solved the problem.
Seede
"Andrews, Chris" wrote:
> Dunno about quickly, but I usually do something like this (before slapping
> myself in
A. Kretschmer wrote:
am Wed, dem 13.09.2006, um 15:46:58 -0700 mailte Junkone folgendes:
hI
i have a bad situation that i did not have primary key. so i have a
table like this
colname1colname2
1 apple
1 apple
2
Dunno about quickly, but I usually do something like this (before slapping
myself in the face for getting into that state):
CREATE TABLE tn_backup AS SELECT DISTINCT * FROM tn;
TRUNCATE TABLE tn;
INSERT INTO tn VALUES SELECT * from tn_backup;
(Where "tn" is the table name)
May not be the best w
If you have a primary key value (or OID?) then you can delete the
duplicates in situ using something like (untested)
-- should work if never more than 1 duplicate row for colname1, colname2
delete from table where pk_value in (
select min(pk_value)
from table
group by colname1, colname2
having
am Wed, dem 13.09.2006, um 15:46:58 -0700 mailte Junkone folgendes:
> hI
> i have a bad situation that i did not have primary key. so i have a
> table like this
> colname1colname2
> 1 apple
> 1 apple
> 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/13/06 19:36, ljb wrote:
> [EMAIL PROTECTED] wrote:
>> hI
>> i have a bad situation that i did not have primary key. so i have a
>> table like this
>> colname1colname2
>> 1 apple
>> 1
