From: | Daniel Sjölie <deepone(at)acc(dot)umu(dot)se> |
---|---|
To: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Cc: | deepone(at)shaolie(dot)dhs(dot)org |
Subject: | Modifying triggers in database in use... |
Date: | 2000-08-16 13:31:15 |
Message-ID: | 20000816153115.A8771@montezuma.acc.umu.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I've sent this once before but it didn't seem to get through
(couldn't find it in the archive)
Hi...
What is the recommended way to make changes to a database in use?
The database is not critical, I can take it down for a day or so but I'd
rather not (or as little as possible anyway). What bothers me is how
hard it is to update functions (primarily triggers) in a nice way.
Using a procedural language is a lot easier but I find it a real pain to
edit functioins created in this way since they're only stored in the
database. You have to retrieve them, edit them and then update them.
Is there a nice way to keep the source elsewhere and reload it in some
simple way? I tried editing database dumps but that feels really bad.
Or would You reccomend that I just get a grip and code it all in C?
(I started but my lazy self really doesn't like it when I know it can be
done so much easier in a procedural language :)
/Daniel (not subscribed)
PS pl/perl doesn't seem to work in debian. Any tips?
--
Now take a deep breath, smile and don't take life so seriously... :)
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Tille | 2000-08-16 13:36:42 | Is this the wrong list? |
Previous Message | Oakley | 2000-08-16 13:06:39 | List of Large sites using Postgres |