Gary Stainburn <[EMAIL PROTECTED]> writes:
> goole=# update requests set r_chassis = 'GAJD7P26209' where r_id = 18560;
> ERROR: attribute 7 has wrong type
> DETAIL: Table has type character varying, but query expects character
> varying.
This looks like a bug that was fixed awhile ago.
I am trying to update a table and I'm getting an odd error. I've narrowed it
down to one attribute, but can't see what the prolem is.
Anyone got any ideas?
goole=# update requests set r_chassis = 'GAJD7P26209' where r_id = 18560;
ERROR: attribute 7 has wrong type
DETAIL: Table has type charac
I am getting an odd error.
Same data loaded on windows does not give it and even going
from a client over VLAN does not give it, so I am guessing it is based on
timing or something.
Microsoft
Cursor Engine error '80004005'
Data
provider or other service returned an E_FAIL status.
/app
Tom Lane wrote:
Good catch. But why are you using a hash index for this?
Just experimenting - I was trying to determine whether a hash index
would give better performance - the values are always unique except when
they're 0 and < > relations are never needed. That particular query
would have be
Marinos Yannikos <[EMAIL PROTECTED]> writes:
> Shouldn't PostgreSQL behave in a different way in this case? (e.g. just
> not use the index):
Good catch. But why are you using a hash index for this?
regards, tom lane
---(end of broadcast)-
Shouldn't PostgreSQL behave in a different way in this case? (e.g. just
not use the index):
Table "public.forum_messages"
message_id | integer | not null default
nextval('forum_messages_message_id_seq'::text)
parent_userid
