Skip to content
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

dev/core#2558 Insert blank MYSQLTIMESTAMP fields as NULL rather than 0 #319

Merged
merged 2 commits into from
Apr 28, 2021

Conversation

ufundo
Copy link
Contributor

@ufundo ufundo commented Apr 24, 2021

Extends the behaviour for date fields to timestamp fields also. This was hinted at in the comment but maybe there was a reason not to?

Seems to fix https://lab.civicrm.org/dev/core/-/issues/2558 for me, but is way out of my comfort zone!

seamuslee001 and others added 2 commits April 14, 2021 08:55
Propose extending the behaviour for date fields to timestamp fields also. This was hinted at in the comment but maybe there was a reason not to?

Fixes https://lab.civicrm.org/dev/core/-/issues/2558 for me at any rate...
@civicrm-builder
Copy link

Can one of the admins verify this patch?

@civibot
Copy link

civibot bot commented Apr 24, 2021

(Standard links)

@demeritcowboy
Copy link
Contributor

Cross-referencing: civicrm/civicrm-core#20113

Jenkins test this please (I can't remember if tests run on civicrm-packages)

@demeritcowboy
Copy link
Contributor

Jenkins add to whitelist ?

@seamuslee001
Copy link
Contributor

@demeritcowboy do you want to try that last command again pls

@demeritcowboy
Copy link
Contributor

Jenkins add to whitelist ?

@demeritcowboy demeritcowboy changed the base branch from master to 5.37 April 27, 2021 21:58
@civibot civibot bot added 5.37 and removed master labels Apr 27, 2021
@eileenmcnaughton eileenmcnaughton changed the title Insert blank MYSQLTIMESTAMP fields as NULL rather than 0 dev/core#2558 Insert blank MYSQLTIMESTAMP fields as NULL rather than 0 Apr 27, 2021
@eileenmcnaughton
Copy link
Contributor

tests failed - wonder why - definitely relates

@seamuslee001
Copy link
Contributor

@eileenmcnaughton these are potentially flakey tests going to run it again just to be sure

@seamuslee001
Copy link
Contributor

Jenkins re test this please

@seamuslee001
Copy link
Contributor

Looks like test fails were the second barrier issue rather than this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants