Skip to content
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.

Sign up for GitHub

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

Jump to bottom

litebans support bug [Table column names are not updated properly] #1355

Closed
RimuruChan opened this issue Mar 6, 2020 · 2 comments
Closed

litebans support bug [Table column names are not updated properly] #1355

RimuruChan opened this issue Mar 6, 2020 · 2 comments
Labels
Bug Issues that contain unintended behavior DataExtensions Tickets related to DataExtensions p: 25 Story points estimate for work required for implementing this issue. Consider splitting smaller.
Projects
Backlog (Bugs)

Comments

@RimuruChan
Copy link

Describe the issue

the column is not aligned
image

Server information

服务器 Information

Plan 版本: 5.0 build 415
服务器: BungeeCord git:Travertine-Bootstrap:1.15-SNAPSHOT:8e3fe77:128 (git:Travertine-Bootstrap:1.15-SNAPSHOT:8e3fe77:128)
Database: MySQL

Operating SubSystem: Windows 服务器 2019 (amd64) version 10.0
Java 版本: 1.8.0_241, Oracle Corporation
Java VM 版本: Java HotSpot(TM) 64-Bit 服务器 VM version 25.241-b07, Oracle Corporation

Benchmarks

35 ms      -1 MB   subsystem-enable

Exceptions & Other Logs

Additional information
@RimuruChan
Copy link
Author

Title and content do not correspond

@AuroraLS3 AuroraLS3 added Bug Issues that contain unintended behavior DataExtensions Tickets related to DataExtensions labels Mar 7, 2020
@AuroraLS3 AuroraLS3 changed the title litebans support bug litebans support bug [Table column names are not updated properly] Mar 7, 2020
@AuroraLS3 AuroraLS3 added this to Current Cycle in Active Development Mar 13, 2020
@AuroraLS3
Copy link
Collaborator

AuroraLS3 commented Mar 13, 2020 •
edited

Looks like the issue happens because two methods are the same name with different parameters and Plan doesn't distinguish between the two in the database. Because a player's table is updated more frequently the player table's columns are shown on the server page.

@AuroraLS3 AuroraLS3 added the p: 25 Story points estimate for work required for implementing this issue. Consider splitting smaller. label Mar 13, 2020
@AuroraLS3 AuroraLS3 mentioned this issue Mar 20, 2020
Closed
@AuroraLS3 AuroraLS3 added this to Priority MEDIUM in Backlog (Bugs) Mar 31, 2020
Backlog (Bugs) automation moved this from Priority MEDIUM to Done May 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Issues that contain unintended behavior DataExtensions Tickets related to DataExtensions p: 25 Story points estimate for work required for implementing this issue. Consider splitting smaller.
Projects
No open projects
Backlog (Bugs)
  
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AuroraLS3 @RimuruChan