This new table will be used to store links and collect data about their usages.
Details
Details
Run migration and check if the table was created. Create a new db and check if that also creates this table.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| keyserver/src/database/migration-config.js | ||
|---|---|---|
| 342 ↗ | (On Diff #25333) | At some point the designs contained a list of expired links where the reason was present. One of the reasons that could be put here was manual expiration. But probably we shouldn't prioritize it - going to delete it for now, and if we ever decide to include it, we can do that. |
| 347 ↗ | (On Diff #25333) | Yeah, the result is what you described. This is a mistake on my part, as this should be an ordinary index, and not the unique one. Furthermore, this index should also contain a primary flag as the second field, because it should support two queries: one for all the links from a community, and one for its primary link. |
Comment Actions
Fix the index and delete unnecessary field. Tested this change by droping a table and running the migration. I have to test creating a fresh db - going to do that before
landing.