Skip to content

EROPSPT-717: Make retention status nullable and remove fields from entities#210

Open
aleyipsoftwire wants to merge 1 commit into
mainfrom
remove-retention-status
Open

EROPSPT-717: Make retention status nullable and remove fields from entities#210
aleyipsoftwire wants to merge 1 commit into
mainfrom
remove-retention-status

Conversation

@aleyipsoftwire

@aleyipsoftwire aleyipsoftwire commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Describe your changes

These columns aren't used anywhere, so cleaning them up.

I've added the manual script to delete the columns here: https://mhclgdigital.atlassian.net/wiki/spaces/ED1/pages/932217119/Release+-+EROP+3.65+-+11+06+2026#Pre-release-Instructions

Subsequent PR: #211

Issue ticket number and link

https://mhclgdigital.atlassian.net/browse/EROPSPT-717

Checklist before requesting a review

Tick all those which are done
Replace check box with ❌ if the step is not relevant for this PR

  • I double checked that ACs on the ticket are met by this code update
  • I have checked any risky steps with my TL (cheat sheet for safe release here)
  • ❌ I have updated the relevant yml versions
  • I have added tests to new code and updated existing tests where needed
  • I have checked complies with security policy and data protection policy
  • Code reviewer has verified during code review the relevant controls and practices for the two policies mentioned above
  • I have documented any release dependencies (e.g. service release order or incompatible versions) in the Release notes
    • Can leave tags as tbd until merged

@aleyipsoftwire aleyipsoftwire self-assigned this Jun 4, 2026
@aleyipsoftwire aleyipsoftwire force-pushed the remove-retention-status branch from dc93746 to c864307 Compare June 4, 2026 15:32

@emisto3 emisto3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I think this will need to split into 2 releases 😢
Also the 3.65 release is pretty big, please can we do this in 3.66 and 3.67 (and therefore move the pre-release steps)

xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.1.xsd">

<changeSet author="alex.yip@softwire.com" id="0042_EROPSPT-717_remove_unused_columns_from_postal" context="ddl">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we know how big the DB is and how many rows will need to be done? Could this time out?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Postal is about 5 million rows, proxy about 50k, all rows will be affected. Would be easy to run this manually before deploying if you think it's worth it

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it isn't worth the risk, please can you add it to the pre release steps?
Also do we need to worry about locking the DB?

@aleyipsoftwire aleyipsoftwire force-pushed the remove-retention-status branch from c864307 to ba94ba4 Compare June 5, 2026 13:27
@aleyipsoftwire aleyipsoftwire changed the title EROPSPT-717: Remove unused postal and proxy application data retention columns EROPSPT-717: Make retention status nullable and remove fields from entities Jun 5, 2026
@aleyipsoftwire aleyipsoftwire force-pushed the remove-retention-status branch from ba94ba4 to e15e939 Compare June 5, 2026 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants