Migrate sql queries from sqlserver to LabKey SQL syntax - #1854
Open
ankurjuneja wants to merge 18 commits into
Open
Migrate sql queries from sqlserver to LabKey SQL syntax#1854ankurjuneja wants to merge 18 commits into
ankurjuneja wants to merge 18 commits into
Conversation
|
WARNING: This PR appears to have the default title generated by GitHub. Please use something more descriptive. |
ankurjuneja
changed the title
ankurjuneja
marked this pull request as ready for review
August 24, 2026 19:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
These queries were written against SQL Server and rely on behaviour PostgreSQL doesn't share i.e. implicit type coercion, case-insensitive collation, and T-SQL-only functions. This migrates them to portable LabKey SQL (explicit casts, typed NULLs in UNION branches, LOWER() on both sides of case-sensitive comparisons, chr()/LOCATE in place of T-SQL equivalents) so the ONPRC modules behave identically on both databases.
Related Pull Requests
Changes
Tasks 📍