> If you have databases that are dependent on each others data you should
> probably move those databases into a new schema within one database...
That's a non-trivial task, especially if some of the tables in the
two databases have the same name.
--
Mike Nolan
---(end o
Mike Nolan wrote:
If you have databases that are dependent on each others data you should
probably move those databases into a new schema within one database...
That's a non-trivial task, especially if some of the tables in the
two databases have the same name.
Migrating from one database t
Eric Jones wrote:
We are migrating from Informix to Postgres 7.4.7 and are having a
difficult time finding if postgres can insert/update tables across
different databases. Namely using functions/triggers when an
update/insert is performed on a table it updates/inserts in a table on a
different
Eric Jones wrote:
We are migrating from Informix to Postgres 7.4.7 and are having a
difficult time finding if postgres can insert/update tables across
different databases. Namely using functions/triggers when an
update/insert is performed on a table it updates/inserts in a table on a
different
On Wed, 2005-05-25 at 07:08, Eric Jones wrote:
> We are migrating from Informix to Postgres 7.4.7 and are having a
> difficult time finding if postgres can insert/update tables across
> different databases. Namely using functions/triggers when an
> update/insert is performed on a table it update
We are migrating from Informix to Postgres 7.4.7 and are having a
difficult time finding if postgres can insert/update tables across
different databases. Namely using functions/triggers when an
update/insert is performed on a table it updates/inserts in a table on a
different database. Informix
Oh, and one other thing...
The example has a typo. In the function, 'temp' and 'cust' should be the
same variable (doesn't matter what it's called).
Cheers,
Ed Loehr
Ed Loehr wrote:
> Sarah Officer wrote:
>
> > Can anyone set me straight here? An example of a trigger which
> > calls a sql pr
Sarah Officer wrote:
> Can anyone set me straight here? An example of a trigger which
> calls a sql procedure would be much appreciated! I'd like the
> function to be able to access the rows which are being removed.
How about examples of a trigger that calls a *PL/pgSQL* procedure that
has acc
Hi,
I'm porting a database from Oracle, and I'm having difficulty
working out the syntax & logic for porting the triggers.
Here's an example of what I have in Oracle:
create table Images (
id varchar(100) PRIMARY KEY,
title varchar(25)NOT NULL,
filepath va
