Skip to content

Conversation

@labkey-adam
Copy link
Contributor

INSERT INTO mergesync.testnamemapping (servicename, mergetestname, automaticresults) VALUES ('Urinalysis', 'URINE', false);
INSERT INTO mergesync.testnamemapping (servicename, mergetestname, automaticresults) VALUES ('Yersinia culture', 'YERSNA', false);

TRUNCATE TABLE mergesync.mergetolkmapping;
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not understanding why this line is getting deleted. In the normal bootstrap scenario, mergesync-0.04-0.05.sql will have inserted rows.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The table was dropped and recreated just before this INSERT chunk, so the TRUNCATE is a no-op. Not causing any harm, of course.

@labkey-adam labkey-adam merged commit 52337d0 into develop Aug 1, 2025
10 checks passed
@labkey-adam labkey-adam deleted the fb_migrate_ss_to_pg branch August 1, 2025 21:48
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.

3 participants