Re: [Chasers-general] code update

[Jonathan H. <jhe...@de...>]

Nicholas Burmeister wrote:
> Ok, I ran both scripts; the table logging one spewed a bunch of output, some of it past the buffer. It all looks more or less ok, to my perception, except for the very last lines of output:
>
> CREATE RULE tbl_user_login_log_log_noupdate AS<br />
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ON UPDATE TO tbl_user_login_log_log DO INSTEAD NOTHING; COMMIT <br>The Postgres SQL server reported an error.<br>The error text was: ERROR:  duplicate key violates unique constraint "db_revision_history_pkey"<br>The program is continuing</div>
>
>   
This duplicate key violation indicates that the script was already run
once. You can verify if table logging is enabled by running this command
from psql:

CHASERS=> \d tbl_staff

you'll get a bunch of output describing the table, and then the last few
lines will look like this if table logging is enabled (the specific
trigger is "tbl_staff_log_chg", listed third)

Triggers:
    tbl_staff_changed_at_update BEFORE UPDATE ON tbl_staff FOR EACH ROW
EXECUTE PROCEDURE auto_changed_at_update()
    tbl_staff_insert AFTER INSERT ON tbl_staff FOR EACH ROW EXECUTE
PROCEDURE add_user_option_record()
    tbl_staff_log_chg AFTER INSERT OR DELETE OR UPDATE ON tbl_staff FOR
EACH ROW EXECUTE PROCEDURE table_log()

> [root@pchqweb chasers]#
>
> Not sure if this is important or not. 
>
> The second script, the enable_changed_at_trigger.php, ran without a single line of output. Not sure if that's ok or not.
>
>   
I think no output means it ran successfully, but if it isn't enabled,
you won't see the tbl_staff_changed_at_update trigger listed when you do
"\d tbl_staff" as described above.

-Jonathan