Page MenuHomePhabricator

Fix SQL issue with Ponder migration
ClosedPublic

Authored by chad on Aug 8 2015, 5:56 PM.
Tags
None
Referenced Files
F13179295: D13830.diff
Wed, May 8, 9:05 PM
Unknown Object (File)
Sat, May 4, 6:31 PM
Unknown Object (File)
Wed, May 1, 11:06 AM
Unknown Object (File)
Wed, Apr 24, 11:41 PM
Unknown Object (File)
Apr 11 2024, 7:58 AM
Unknown Object (File)
Apr 1 2024, 9:56 PM
Unknown Object (File)
Mar 15 2024, 10:14 PM
Unknown Object (File)
Mar 6 2024, 4:58 AM
Subscribers

Details

Reviewers
epriestley
Commits
Restricted Diffusion Commit
rP736bda7081c9: Fix SQL issue with Ponder migration
Summary

This fails to apply on my second sandbox with incorrect DOUBLE value. Reran SQL, works as expected.

Test Plan

Rerun new SQL on ponder_question table

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

chad retitled this revision from to Fix SQL issue with Ponder migration.
chad updated this object.
chad edited the test plan for this revision. (Show Details)
chad added a reviewer: epriestley.
epriestley edited edge metadata.
This revision is now accepted and ready to land.Aug 8 2015, 5:56 PM

Does the = 0 thing also need = '0' maybe?

It ran fine for me, but maybe it's best to do the quotes anyway? We convert the column first.

chad edited edge metadata.
  • Update 0 as well

Do you have somewhere to test this for sanity?

This revision was automatically updated to reflect the committed changes.

You can re-apply the patch as a general sanity check with bin/storage upgrade --apply phabricator: 20150806.ponder.status.2.sql.

MySQL might be a bit loose about typecasting 0, I'm not sure. I'll yell if this does naything bad on this server.