Fix: Resolved outfit saving/loading issues for legacy & migrated databases (#4)#5
Open
CheloLima wants to merge 3 commits into
Open
Fix: Resolved outfit saving/loading issues for legacy & migrated databases (#4)#5CheloLima wants to merge 3 commits into
CheloLima wants to merge 3 commits into
Conversation
Add Auto SQL DB Fix (Migration)
Fixed PlayerOutfit Saves :-)
Fixes new getOutfitForPLayer for old Skin Menus...
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.
This PR addresses Issue #4, where outfits fail to save due to missing columns or strict legacy column constraints (e.g., from older clothing systems).
Key Features:
componentsandpropscolumns if they are missing in theplayer_outfitstable.outfitIdcolumn to be nullable, preventing SQL insertion errors during migration from older versions.server.luato load legacy outfits from the singleskincolumn if the newer separate columns are empty.components,props) and the legacyskincolumn to ensure no data is lost.This ensures a smooth experience for all users, regardless of whether they are performing a fresh install or migrating from an older system.