Skip to content

Conversation

@Tomdango
Copy link
Contributor

Description

Context


Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@Tomdango Tomdango force-pushed the task/FTRS-1485-fix-etl-end-to-end branch from b61052b to d99e2e0 Compare November 17, 2025 12:23
Copy link
Contributor

@prjh2-nhs prjh2-nhs left a comment

Choose a reason for hiding this comment

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

nice PR 😎 (just one comment 🧐)

raise ValueError(
"Invalid DataMigrationConfig: db_config.connection_string must be a non-empty string"
)
self.engine = create_engine(connection_string, echo=False)
Copy link
Contributor

Choose a reason for hiding this comment

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

For the "Recreate Legacy Service Model to remove SQLAlchemy tracking" in ticket, mentions:

  • "postgresql_readonly execution option should be added to the database connection to ensure any update interactions are immedately rejected by the database to prevent this issue from being reintroduced."

^ would that be here? 🤔

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