well i got a trace of the SQL commands sent to the server:
2006-11-20 16:06:51 LOG: statement: PREPARE <unnamed> AS create local temporary table HT_item (ID BIGINT not null) on commit drop
2006-11-20 16:06:51 LOG: PARSE MESSAGE STATISTICS
2006-11-20 16:06:51 LOG: statement: <BIND>
2006-11-20 16:06:51 LOG: statement: EXECUTE <unnamed> [PREPARE: create local temporary table HT_item (ID BIGINT not null) on commit drop]
2006-11-20 16:06:51 LOG: QUERY STATISTICS
2006-11-20 16:06:51 LOG: statement: PREPARE <unnamed> AS insert into HT_item select itemimpl0_.ID as ID from item itemimpl0_ where ID in ($1)
2006-11-20 16:06:51 ERROR: relation "ht_item" does not exist
2006-11-20 16:06:51 LOG: statement: PREPARE <unnamed> AS drop table HT_item
2006-11-20 16:06:51 LOG: PARSE MESSAGE STATISTICS
2006-11-20 16:06:51 LOG: statement: <BIND>
2006-11-20 16:06:51 LOG: statement: EXECUTE <unnamed> [PREPARE: drop table HT_item]
2006-11-20 16:06:51 ERROR: table "ht_item" does not exist
I think that the problem is in "on commit drop", because i excecute this statment in the query browse of pgAdmin III and happens the same, What I must modify?
2006/11/20, Heikki Linnakangas <heikki@enterprisedb.com>:Pablo Araujo wrote:
> ok, but this assumes that being created everything in the same session.
>
> that is to say, it creates it, it inserts data and it destroys it in the
> same session.
Can you get a trace of the SQL commands sent to the server? One way to
get that is to set the log_statement configuration parameter in your
postgresql.conf file to "all".
That would help diagnosing the problem.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
