Signal-iOS/SignalServiceKit
Evan Hahn 7efe024940 Explain why a migration lacks a column type
This change should have no user impact.

I created a column in 8d707a9c74. I wanted
it to be a `BLOB`. I succeeded because [SQLite chooses `BLOB` by
default][0], but I wish I had been explicit.

I *could've* updated the migration, but didn't want to make a mistake
and cause divergent migrations. Instead, I added a comment.

I also updated a test.

[0]: https://www.sqlite.org/datatype3.html#determination_of_column_affinity
2023-02-06 08:34:00 -08:00
..
Calls Enable a RingRTC field trial for all users, with kill switch 2023-02-01 16:20:16 -06:00
Dependencies Support for re-registration 2023-02-02 10:17:52 -08:00
Experience Upgrades Migrate KeyBackupService to the Swift Way™️ 2023-02-02 09:42:05 -08:00
Jobs Add all JobQueues to environment, via a wrapper 2022-11-09 14:08:44 -06:00
KeyBackupService Support for re-registration 2023-02-02 10:17:52 -08:00
protobuf Add spam reporting tokens 2023-01-25 14:14:57 -06:00
Resources Show video duratioin in All Media. 2023-02-03 16:00:46 -08:00
src Explain why a migration lacks a column type 2023-02-06 08:34:00 -08:00
tests Explain why a migration lacks a column type 2023-02-06 08:34:00 -08:00
.clang-format Update clang-format with AllowShortEnumsOnASingleLine: false 2022-03-14 11:20:20 -07:00
.gitignore
.travis.yml
SignalServiceKit-Prefix.pch Change license to AGPL 2022-10-13 08:25:37 -05:00
SignalServiceKit.h Call Disposition 2023-01-10 11:48:46 -08:00