Thread: RE: Creating Users

Miguel Gonzalez writes:

> Could you be a bit more specific? Time to upgrade to what?

PostgreSQL

--
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter

Could you be a bit more specific? Time to upgrade to what?

Many thanks Miguel

----- Original Message -----
From: Peter Eisentraut <peter_e@gmx.net>
To: Miguel Gonzalez <jffernandez@usuarios.retecal.es>
Cc: PostgreSqlAdmin <pgsql-admin@postgresql.org>
Sent: Monday, August 20, 2001 7:25 PM
Subject: Re: [ADMIN] Creating Users


> Miguel Gonzalez writes:
>
> >  I am developing a client application with C++ Builder 3 to access a
> > Database designed with PostgreSQL 7.0.4 using a BDE alias through the
ODBC
> > driver.
>
> Time to upgrade.
>
> --
> Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>

I have a set of rules that worked in 7.0.3 for async notification.  Those
same set of rules don't seem to be working under 7.1.2.  The rules look
like this.

CREATE RULE CONFIG_CHNG AS ON INSERT TO gs_config DO (NOTIFY CONFIG_CHANGE);
CREATE RULE CONFIG_CHNG AS ON UPDATE TO gs_config DO (NOTIFY CONFIG_CHANGE);
CREATE RULE CONFIG_CHNG AS ON DELETE TO gs_config DO (NOTIFY CONFIG_CHANGE);

Here is a look at what my session looks like.

bash# psql config
Welcome to psql, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help on internal slash commands
       \g or terminate with semicolon to execute query
       \q to quit

config=# insert into gs_config values ('Life','42');
INSERT 18842 1
config=# update gs_config set config_value='0' where config_name='Life';
ERROR:  Conditional NOTIFY is not implemented
config=# delete from gs_config where config_name='Life';
ERROR:  Conditional NOTIFY is not implemented
config=# \q


Obviously, this isn't what I desired to have happen.  :)  Anyone have any
ideas on either a way that I can get around this little feature?  I really
really need the async notification stuff.

Thanks,
Matthew M. Copeland

matthew.copeland@honeywell.com writes:
> I have a set of rules that worked in 7.0.3 for async notification.  Those
> same set of rules don't seem to be working under 7.1.2.

They weren't really working right in 7.0 either, but they coincidentally
failed to crash.

I'd suggest using a trigger that does NOTIFY, instead.

            regards, tom lane

> They weren't really working right in 7.0 either, but they coincidentally
> failed to crash.
>
> I'd suggest using a trigger that does NOTIFY, instead.
>

Wonderful.  I have been using them for about the last 6 months without any
problems, and now someone mentions this feature.  I will look into the
trigger stuff, and see what I can figure out.  Thanks.

Matthew M. Copeland