jesjos / jesjos/active_record_upsert

Upsert nil in place of current value

Open
#88 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
207
Forks
49
PR merge metrics
No merged PRs in 30d

Description

I'm running an upsert that replaces the current value (e.g. a non-nil value) with a nil, but the nil fails to get upserted. Upserts of any other value seems to work. Is this unexpected behavior? Am I missing something?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported upsert that replaces a non-nil value with nil, comparing it with upserts of other values. The issue is resolved when the nil value is successfully persisted and the behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
backend, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.