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_201002 to session_201002 very fine, but that just not what I would like to have. On Wed, Feb 3, 2010 at 00:55, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Clemens Schwaighofer <clemens_schwaighofer@xxxxxxxxxxx> 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 triggers. > As-is they'll be sensitive to whatever your search_path is. > > regards, tom lane > -- ★ Clemens 呉 Schwaighofer ★ IT Engineer/Web Producer/Planning ★ E-Graphics Communications SP Digital ★ 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ★ Tel: +81-(0)3-3545-7706 ★ Fax: +81-(0)3-3545-7343 ★ http://www.e-gra.co.jp This e-mail is intended only for the named person or entity to which it is addressed and contains valuable business information that is privileged, confidential and/or otherwise protected from disclosure. If you received this e-mail in error, any review, use, dissemination, distribution or copying of this e-mail is strictly prohibited. Please notify us immediately of the error via e-mail to disclaimer@xxxxxxxxxxxxx and please delete the e-mail from your system, retaining no copies in any media. We appreciate your cooperation. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
