David Kerr wrote:
On Wed, Sep 02, 2009 at 11:44:20PM -0500, Adam Rich wrote:
- In Oracle, the way we handle audit triggers is by using Package
- Variables. We emulate some of that functionality in postgresql by
- adding a custom variable to the configuration file:
-
- custom_variable_classes
On Wed, Sep 02, 2009 at 11:44:20PM -0500, Adam Rich wrote:
- In Oracle, the way we handle audit triggers is by using Package
- Variables. We emulate some of that functionality in postgresql by
- adding a custom variable to the configuration file:
-
- custom_variable_classes = 'mysess'
-
- Then
> Most of the time, my application will set the edited_by field to
> reflect an application username (i.e., the application logs into the
> database as a database user, and that's not going to be the
> application user) So I log into my application as "Dave", but the
> application connects to the
On Fri, Aug 28, 2009 at 08:07:40PM +0100, Simon Riggs wrote:
-
- On Fri, 2009-08-28 at 08:50 -0700, David Kerr wrote:
-
- > so, is there a way in a trigger to know if edited_by is expressly
- > being set in the update statement? it seems like if I can know that,
- > then i should be able to figu
On Fri, 2009-08-28 at 08:50 -0700, David Kerr wrote:
> so, is there a way in a trigger to know if edited_by is expressly
> being set in the update statement? it seems like if I can know that,
> then i should be able to figure it out.
No, but you could use a before trigger to reset the value to
all of my tables have 4 fields
edited_by
edited_date
created_by
created_date
Most of the time, my application will set the edited_by field to reflect
an application username (i.e., the application logs into the database as
a database user, and that's not going to be the application user)
So I lo
