Hey everybody. I've got a strange one today. I'm trying to convert an extremely messy access sql query into something that can be used with our postgresql database (the pgsql db is being built to replace the access db). I had barely begun trying to convert it when I was confronted with this error message:

column "isactive" of relation "membermailingaddress" does not exist

However, a quick \d in psql let's me know that there is indeed a field "isactive" on that specific table. I can't begin to imagine why it would throw an error like this.

Here's my psql output, with a simple test query to reproduce the issue, and a \d membermailingaddress afterwards. Anybody have any ideas?

current=# insert into membermailingaddress(
current(# mb_cn_num,
current(# mb_acct_num,
current(# IsActive,
current(# IsMember
current(# )
current-# VALUES
current-# (
current(# 1,
current(# 1500.0,
current(# TRUE,
current(# FALSE
current(# )
current-# ;
ERROR:  column "isactive" of relation "membermailingaddress" does not exist
LINE 4: IsActive,
       ^
current=# \d membermailingaddress
   Table "public.membermailingaddress"
    Column      |     Type     | Modifiers
-----------------+--------------+-----------
mb_cn_num       | integer      |
mb_acct_num     | numeric(6,1) |
IsActive        | boolean      |
IsMember        | boolean      |
IsMail          | boolean      |
IsPromoMail     | boolean      |
HouseholdID     | numeric      |
HouseholdSize   | integer      |
Name1           | text         |
Name2           | text         |
Addr1           | text         |
Addr2           | text         |
Addr3           | text         |
City            | text         |
State           | text         |
Zip             | text         |
Zip5            | text         |
xxPrimaryName   | text         |
xxJointName     | text         |
xxHouseholdHash | text         |

current=#

TIA

Thomas R. Hart II
[EMAIL PROTECTED]

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
      choose an index scan if your joining column's datatypes do not
      match

Reply via email to