Hi,
I've not found, as reported into postgresql docs, 'infinity':
create temp table subscriptions (
id int references people,
expire date default 'infinity');
ERROR: Unrecognized date external representation 'infinity'
Is there someone that knows the new costant name?
>From PostgreSQL d
On Tue, 2 Jan 2001, Macky wrote:
> Is there a function in SQL that does autoincrementing...
http://www.postgresql.org/docs/faq-english.html#4.16.1
and
http://www.postgresql.org/users-lounge/docs/7.0/postgres/sql-createsequence.htm
will tell you how to do this.
-- Brett
It should work if you remove all three triggers for the constraint
using drop trigger, don't delete rows from pg_trigger unless you go
through and manually change the row in pg_class for the relation
the trigger is for.
On Mon, 1 Jan 2001, Michael Davis wrote:
> Does anyone know how to complete
Is there a function in SQL that does autoincrementing...
eg.
CREATE TABLE (name varchar(40),num_id int);
wherein num_id starts with 0 and then when ever I INSERT another record
num_id goes 1 etc
Thanks in advance
Does anyone know how to completely and accurately remove or drop a
constraint, specifically a foreign key constraint? I tried to remove a
constraint by deleting it's trigger from pg_triggers. This caused some
undesirable side effects with other tables involved with the constraint. I
have se
Ferruccio Zamuner <[EMAIL PROTECTED]> writes:
> Is this a bug?
No, but it is a missing feature: there's no way to reset a sequence's
is_called flag once it's been set. This is fixed for 7.1: there's now
a three-parameter variant of setval() to let you do exactly that.
Try doing the two inserts in one rule:
CREATE RULE ... DO INSTEAD
(
INSERT INTO ... ;
INSERT INTO ... ;
);
This is the only way of controlling the order in which the actions will
be done; separate rules will be applied in an undefined order.
regards, tom lane
Hi,
#create temp table a (
id serial primary key,
name text not null);
#insert into a (name) values ('Tom');
#insert into a (name) values ('Fer');
#insert into a (name) values ('Mario');
#select * from a;
id | name
+---
1 | Tom
2 | Fer
3 | Mario
(3 rows)
OK. Now
I just answered my question. For anyone how may be interested, here is the
answer. The following create rule allows multiple actions. This was not
very clear from the documentation. Would some be willing to suggest to the
documentation group to add an example of a rule with multiple actions
How do I create a rule for a view that inserts into two tables?
I have a view based on two tables. I would like to create insert, update,
and delete rules for this view to:
- update both tables when the view is updated
- delete from both tables when a record is deleted from the view
- insert i
10 matches
Mail list logo
