-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty Entries With Black Listing #53
Comments
Looks good to me. Except from the second argument: it should be either 'updated_at' (if you want to use
Looks like a bug: if everything is filtered out we still add a log entry. @charlie-wasp Could you, please, take a look? |
|
I made the null change and it it still generating empty change versions.
|
@palkan I‘m on it! |
Fixed by #55 and released as 0.6.2 |
I track a position in a list and the status of data display in a table row.
execute <<-SQL CREATE TRIGGER logidze_on_brokerage_transactions BEFORE UPDATE OR INSERT ON brokerage_transactions FOR EACH ROW WHEN (coalesce(#{current_setting('logidze.disabled')}, '') <> 'on') EXECUTE PROCEDURE logidze_logger(100, 'updated_at', '{created_at, position, stale}'); SQL
The position and stale get updated a lot - and they don't actually matter to the audit. I ended up with a bunch of records that just have the updated_at as the changed field. I then change it to:
EXECUTE PROCEDURE logidze_logger(100, '', '{created_at, position, updated_at, stale}');
Now I have a bunch of change entries with no entries in them. Basically I'm trying to only store changes if there is a change in a field that isn't created_at, position or stale. What should it look like?
The text was updated successfully, but these errors were encountered: