-
Notifications
You must be signed in to change notification settings - Fork 7
Rename tables and columns with names that are too long for PostgreSQL #7458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
labkey-adam
wants to merge
7
commits into
develop
Choose a base branch
from
fb_long_names_to_short
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e956069
Rename tables and columns with names that are too long for PostgreSQL
labkey-adam 1857966
Remove rollbacks. More comments.
labkey-adam 67d650b
Merge remote-tracking branch 'origin/develop' into fb_long_names_to_s…
labkey-adam a055426
Script, module bump, and fix bracketing
labkey-adam c23021b
Generate all storage names using PostgreSQL rules
labkey-adam 43c037e
Transact rename/update pairs. Remove redundant/unneeded code.
labkey-adam 6d752b5
Merge remote-tracking branch 'origin/develop' into fb_long_names_to_s…
labkey-adam File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
18 changes: 18 additions & 0 deletions
18
api/src/org/labkey/api/data/dialect/PostgreSqlService.java
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| package org.labkey.api.data.dialect; | ||
|
|
||
| import org.labkey.api.services.ServiceRegistry; | ||
|
|
||
| public interface PostgreSqlService | ||
| { | ||
| static PostgreSqlService get() | ||
| { | ||
| return ServiceRegistry.get().getService(PostgreSqlService.class); | ||
| } | ||
|
|
||
| static void setInstance(PostgreSqlService impl) | ||
| { | ||
| ServiceRegistry.get().registerService(PostgreSqlService.class, impl); | ||
| } | ||
|
|
||
| BasePostgreSqlDialect getDialect(); | ||
| } |
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
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
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
2 changes: 2 additions & 0 deletions
2
experiment/resources/schemas/dbscripts/sqlserver/exp-26.004-26.005.sql
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| -- SQL Server only | ||
| EXEC core.executeJavaUpgradeCode 'shortenAllStorageNames'; |
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems odd. If it's needed, would it be better to capture them in the
forEach? I don't think we're getting value out of setting it in the DB and then querying the DB for them.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added it to verify that the renaming steps worked as expected. There are a lot of moving parts... especially with the multi-step column-renaming process. The table-renaming steps used to be more complex; I simplified them, but it seemed reasonable to leave the check in.