Skip to content

Change SimpleTableDomainKind to use getValueSql - #1462

Merged
labkey-martyp merged 3 commits into
developfrom
fb_simpletable_getValueSql
Aug 6, 2020
Merged

Change SimpleTableDomainKind to use getValueSql#1462
labkey-martyp merged 3 commits into
developfrom
fb_simpletable_getValueSql

Conversation

@labkey-martyp

Copy link
Copy Markdown
Contributor

Rationale

Looks like SimpleTableDomainKind needs to use getValueSql instead of getSelectName after the related PR.
https://teamcity.labkey.org/repository/download/LabKey_Trunk_LabkeyPremiumTrunk_GitModules_SnprcEhrSqlserver/1080510:id/tomcatLogs.tar.gz!/labkey-errors.log

Related Pull Requests

#1458

Changes

Update SimpleTableDomainKind.sqlObjectIdsInDomain to use getValueSql

@labkey-matthewblabkey-matthewb 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.

It's not obvious, but It is a little suspect to mix and match the SchemaTableInfo (variable table) and a columns from the SimpleTable (variable table). Makes more sense to stick with only objects from table or only objects from schemaTable.

Also avoid using String + SQLFragment. That may not do what you want.

sql.append("SELECT o.ObjectId FROM ").append(table.getFromSql("me")).append(...).append(objectUriColumn.getValueSql("me").append(...)

@labkey-martyp
labkey-martyp merged commit caad27a into developAug 6, 2020
@labkey-martyp
labkey-martyp deleted the fb_simpletable_getValueSql branch August 6, 2020 05:29
cnathe added a commit that referenced this pull request Aug 25, 2026
…r run container (#7979)
## Rationale
LabKey/internal-issues#1462
## Related Pull Requests
- #7979
- LabKey/premiumModules#726
## Changes
- QCStateAction to check for AssayReadPermission for run container
Sign up for freeto 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

@labkey-martyp@labkey-matthewb