On Thursday, October 29, 2015 at 10:49:18 AM UTC-7, Adarsh Pandit wrote:
>
> Not sure if this is Sequel's business, Postgres', or Rails, but here goes:
>
> I'm pulling some sensitive data down from an external API and storing it
> in a JSONB column.
>
> I'm fine with it being not-encrypted in the database (for now), but I'd
> rather it not be logged as such when I do an UPDATE:
>
> Sequel::Postgres::Database (0.9ms) UPDATE "users" SET "updated_at" =
> '2015-10-29
> 10:39:05.088968-0700', "personal_information" = '[{"sensitive_information"
> : "Oh boy is this secret...", etc }]'
>
> Rails' `filter_parameters` has to do with external params coming in and
> not being logged, so this is not the same.
>
> There is a similar question here for ActiveRecord
> <https://stackoverflow.com/questions/13051949/how-to-disable-activerecord-logging-for-a-certain-column>,
>
> but seems to be no easy solution.
>
> I assume this isn't possible in Sequel either, but I figured I'd ask.
> Thanks!
>
You can handle this by using a custom logger that modifies input before
logging. That's probably the best solution if you want to keep logging.
The easiest way to handle it is just to not log any queries.
Thanks,
Jeremy
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.
