[BUGS] rename column and trigger on column

[Chris Sutton]

create table ref_table (
  id serial primary key
  ref_name varchar);

create table data_table (
  a int4 references ref_table);

which of course creates 3 triggers.

If you do:

alter table data_table rename column a to b;

The trigger on data_table still looks for column named "a" so sometime in
the future you will probably get:

ERROR:  constraint : table data_table does not
have an attribute a

Possible solutions, along with telling the db admin to pay attention ;)

1. Check for triggers on column before allowing rename and if they
exist, give a warning of the trigger that needs to be recreated

2. Rebuild the trigger automatically

3. Delete the trigger


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

[BUGS] select real returns nothing

[Chris Sutton]

I'm getting some weird things happen when trying to search for a specific row in a 
table that contains "real" types.

Here is my table structure

table units (
unit_id int4,
price_unit  varchar(10),
unit_covreal,
unit_wt real);

The following row exists in the units table

 unit_id | price_unit | unit_cov | unit_wt
 -++--+-
47430 | LF |   12 |   4.833

The following query returns no rows:

SELECT unit_id FROM units
WHERE price_unit='LF' and unit_cov=12 and unit_wt=4.833;

While these queries return the correct unit_id

SELECT unit_id FROM units
WHERE price_unit='LF' and unit_cov='12' and unit_wt='4.833';

SELECT unit_id FROM units
WHERE price_unit='LF' and unit_cov='12' and unit_wt=float4(4.833);

I'm running pg7.2.1 on Linux.

The curious thing is I have a development database running pg7.1 on linux where I 
don't have this problem.


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org