I tried that too, in all of my trigger functions, it still didn't
change anything.
On Wed, Feb 3, 2010 at 09:42, Tom Lane wrote:
> Clemens Schwaighofer writes:
>> I already tried that. even with prefixing the alter table statement
>> with the schema it does not work.
>
> Not the ALTER TABLE, the
Clemens Schwaighofer writes:
> I already tried that. even with prefixing the alter table statement
> with the schema it does not work.
Not the ALTER TABLE, the insert/update/etc commands inside the trigger
functions.
regards, tom lane
--
Sent via pgsql-general mailing l
I already tried that. even with prefixing the alter table statement
with the schema it does not work.
I suspect that has something to do that when I try to connect eg
visit_201002 with the session table, that there is not data in the
session table itself, but in its subtable, I can connect visit_2
Clemens Schwaighofer writes:
> my problem is, when I insert data into the visit table it tries to
> find the session data in the live schema. I have no idea why, because
> no schema was copied or inherited from the other side.
I think you need to schema-qualify the table names used in the trigger
Hi,
I have a problem with partition tables and schemas
Postgres: 8.4.2 on redhat and debian
I have three schemas public (the default one), live and test
live and test are identical copies in table layout, just the tables
are created for each one sperated.
in those two schemas I have two tables
