From: | Fran Fabrizio <ffabrizio(at)mmrd(dot)com> |
---|---|
To: | Fran Fabrizio <ffabrizio(at)mmrd(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Function created yet not found |
Date: | 2002-03-13 22:01:44 |
Message-ID: | 3C8FCC48.5000107@mmrd.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Call off the dogs. =)
I dug deeper, and found that it wasn't the function that was throwing
the error, but the table it was selecting from. Examining the table
further....
test=# \d entity
Table "entity"
Attribute | Type | Modifier
-----------+-------------------+----------
entity_id | integer |
name | character varying |
type | character varying |
active | boolean |
lft | integer |
rgt | integer |
Indices: entity_findsite_idx,
entity_lft_rgt_idx,
entity_rgt_idx
entity_findsite_idx looked odd to me, not my usual naming scheme.
Co-worker had tested making an index using a function: 'create index
entity_findsite_idx on entity (findsite(entity_id))'. I had since
dropped and reloaded that function, rendering the table useless.
My apologies for prematurely posting. I've never used function-based
indices....would a select findsite(entity_id) from entity actually have
used that index? That could be handy.
Thanks,
Fran
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Shevland | 2002-03-13 22:02:43 | Re: DBvisualizer on MacOS X |
Previous Message | thiemo | 2002-03-13 21:47:01 | Re: [JDBC] Fwd: DBvisualizer on MacOS X |