hmmif you ask me, I would like to suggest add this part in the
fisrt step(create the master table) of 5.9.2 of this doc:
http://www.postgresql.org/docs/9.1/static/ddl-partitioning.html
The doc mentions here that there is no point to define
indexes/constraints on parent table. But it didn't m
Rural Hunter wrote:
> is it worth mentioning in the doc?
Do you have a suggestion for what language you would have found
helpful, or which section(s) of the docs should be modified?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscriptio
yes, I understand that. but is it worth mentioning in the doc?
于2012年3月12日 22:11:16,Kevin Grittner写到:
Rural Hunter wrote:
"triggers are not shared between parent and child tables". is it
true?
Yes.
You can use the same trigger *function* for more than one trigger
though.
-Kevin
--
Se
Rural Hunter wrote:
> "triggers are not shared between parent and child tables". is it
> true?
Yes.
You can use the same trigger *function* for more than one trigger
though.
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
ht
I implemented table partition recently and found that the tiggers on
parent table are not working any more, except the before insert trigger
which redirects data to children table. The after insert/update triggers
are not working now. I understand the after insert trigger may not
working since
Le 28/03/2011 15:44, Shridhar Polas a écrit :
> [...]
> Is there a way to create triggers on system catalog tables like
> pg_class, pg_attribute etc...?
>
No.
--
Guillaume
http://www.postgresql.fr
http://dalibo.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make c
Hi,
Is there a way to create triggers on system catalog tables like
pg_class, pg_attribute etc...?
Thanks,
Shridhar
Resending because I just noticed that the list was not copied on the
rest of the exchange. (Omer, please keep the list copied in any
future exchanges, as it tends to make the discussion available on
search engines for those who may have similar questions.) Omer
wasn't sure about what I was propos
Omer Anson wrote:
> First of all, I apologise if I am posting this in the wrong place.
Not a bad place to start, I guess. If it gets into the realm of an
enhancement request or proposal it might belong on -hackers, but
since you're asking about how it might be done now, this is good.
> I wo
Hello.
First of all, I apologise if I am posting this in the wrong place.
I would like to implement aspect-oriented programming in SQL. To that
end, I figured I need a notification method whenever a stored
procedure is executed (If possible, with rudimentary filtering). I
have seen that this can
Kevin Kempter writes:
> Is it possible to add triggers to system catalog and/or statistics collector
> tables ?
No.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailp
Hi All;
Is it possible to add triggers to system catalog and/or statistics collector
tables ?
Thanks in advance
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
kevin kempter wrote:
> Hi All;
>
> Can I put an update/insert/delete trigger on a BLOB (lo_* style) column,
> It looks like the trigger should actually live on the data column of the
> pg_largeobject table to be effective. Is this correct ?
You can't put a trigger in pg_largeobject. Of course,
Hi All;
Can I put an update/insert/delete trigger on a BLOB (lo_* style)
column, It looks like the trigger should actually live on the data
column of the pg_largeobject table to be effective. Is this correct ?
Thanks in advance...
--
Sent via pgsql-admin mailing list (pgsql-admin@postgres
Hi,
I originally implemented a number of triggers in our production DB using
'plpgsql' and they have been running flawlessly for many years.
It has now become necessary to split up our main DB into a number of
separate DB's.
My question is:
Is it possible for a table insert/update(via trigger)
[EMAIL PROTECTED] (Kailash Vyas) writes:
> hi
> I have a query regarding triggers.
> On INSERT, UPDATE, DELETE I want to fire a trigger to relect it to another
> database on postgres sever.
> how can I do this operation.
> Thanks in advance,
> Kailash Vyas
If you wish the trigger to result in som
On Thu, 8 Sep 2005, Kailash Vyas wrote:
> hi
>
> I have a query regarding triggers.
> On INSERT, UPDATE, DELETE I want to fire a trigger to relect it to another
> database on postgres sever.
> how can I do this operation.
This is tricky, because you probably want to have the same transactional
oc
http://www.google.co.uk/search?hl=en&q=TRIGGER+%2B+postgresql+%2B+8&meta=
which actually will guide you to:
http://www.postgresql.org/docs/current/static/sql-createtrigger.html
..that actually is the pgsql man.
rtfm :)
Best wishes,
Guido
On 9/8/05, Kailash Vyas <[EMAIL PROTECTED]> wrote:
hi
I have a query regarding triggers.
On INSERT, UPDATE, DELETE I want to fire a trigger to relect it to another database on postgres sever.
how can I do this operation.
Thanks in advance,
Kailash Vyas
Stef <[EMAIL PROTECTED]> writes:
> If one has upgraded postgres from 7.1.2 to 7.3.1,
> how does one convert all the triggers that represent
> 7.1.2 foreign keys to actual foreign keys.
The contrib/adddepend module is supposed to help with this
(I've not used it myself though).
If one has upgraded postgres from 7.1.2 to 7.3.1,
how does one convert all the triggers that represent
7.1.2 foreign keys to actual foreign keys.
What I really want to have, is that when I dump the new
upgraded database, that the tables will be dumped with the
original "foreign key" syntax as they
Hi All,
I have table with almost 3,500 records with 9 fields which is similar
structure to Table1. From that I am porting to following structure
Table 1.
T1f1 integer serial (primary key),
T1f2 varchar(100) (unique),
T1f3 integer default 0,
T1f4 text,
T1f5 boolean default 'f',
T1f6 boolean defau
Guys, I've have a legacy summary table ( monitor_summary ) which represents
a count of the number of records in another table ( document_status ).
Here are the table definitions.
CREATE TABLE monitor_summary (
id SERIAL PRIMARY KEY, -- Internal ID
Tim Ellis <[EMAIL PROTECTED]> writes:
> Yeh. Good question. I would assume their generator MEANT
> (max(autonum,0)+1) supposing that a "ANSI Level 2"-compliant server's
> max function might return the second value if the first is NULL. But no
> matter how you slice it, that looks syntactically wro
> > I just used Dezign for Databases and created a simple table in what it
> > claimed was "ANSI Level 2" compliance with a one-up "autonum" column.
>
> There is no such animal as "ANSI Level 2" SQL.
That explains a lot of things. About this DDL problem and Dezign for
Databases both.
> > set (
Tim Ellis <[EMAIL PROTECTED]> writes:
> I just used Dezign for Databases and created a simple table in what it
> claimed was "ANSI Level 2" compliance with a one-up "autonum" column.
There is no such animal as "ANSI Level 2" SQL.
> create trigger transaction_autonum_inc
> before insert on tran
On Thu, 13 Jun 2002, Tim Ellis wrote:
> I just used Dezign for Databases and created a simple table in what it
> claimed was "ANSI Level 2" compliance with a one-up "autonum" column.
>
> It spewed forth the following code:
>
> -- file generated by "dezign for databases"
> -- create-date:6/1
I just used Dezign for Databases and created a simple table in what it
claimed was "ANSI Level 2" compliance with a one-up "autonum" column.
It spewed forth the following code:
-- file generated by "dezign for databases"
-- create-date:6/13/2002
hello!!
If you already have created the triggers functions, the correct
description of this is in the file:
/postgres/postgresql-6.4.2/contrib/spi/REAME
Depending on the type of trigger or integrity to applY , you must
create functions only on the administrator account (.
On Sun, 30 Jan 2000, Mario Simeone wrote:
> I'm using PostgreSQL 6.4.2 on SuSE. I' m trying to create a trigger... but
there are available 6.5.2 rpm version, and 6.5.3 in source.
> postgres says me : Triggers are non implemented yet. These word are also on
> page 114 of Users guide.
> Postgres d
I'm using PostgreSQL 6.4.2 on SuSE. I' m trying to create a trigger... but
postgres says me : Triggers are non implemented yet. These word are also on
page 114 of Users guide.
Postgres doesn't support triggers ?
When ?
32 matches
Mail list logo
