You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose adopting a standardized naming convention for patches in the Individual Progression module to ensure compatibility with AzerothCore's DBUpdater. This tool depends on a specific naming structure to track whether a patch has already been applied, helping manage updates seamlessly.
Suggested Naming Convention
File Naming Format: YYYY_MM_DD_##_xxx.sql
Examples:
2023_06_03_00_patch.sql
2023_06_03_01_patch.sql
Details: The format includes the date (YYYY_MM_DD) followed by a sequence identifier (##) and a brief descriptor (xxx). This structure allows DBUpdater to correctly recognize, sequence, and apply patches.
Key Benefits
DBUpdater Compatibility: Ensures that patches are applied in the intended order, and previously applied patches are correctly recognized, reducing potential update errors.
Consistency and Organization: Facilitates clear organization and sequencing for patches, benefiting both developers and users.
Improved Maintenance: Supports an efficient update process by enabling easy identification and application of patches.
Thank you for considering this proposal. Please reach out if there are any questions or if additional details are needed!
The text was updated successfully, but these errors were encountered:
Hello team,
I propose adopting a standardized naming convention for patches in the Individual Progression module to ensure compatibility with AzerothCore's DBUpdater. This tool depends on a specific naming structure to track whether a patch has already been applied, helping manage updates seamlessly.
Suggested Naming Convention
File Naming Format: YYYY_MM_DD_##_xxx.sql
Examples:
2023_06_03_00_patch.sql
2023_06_03_01_patch.sql
Details: The format includes the date (YYYY_MM_DD) followed by a sequence identifier (##) and a brief descriptor (xxx). This structure allows DBUpdater to correctly recognize, sequence, and apply patches.
Key Benefits
DBUpdater Compatibility: Ensures that patches are applied in the intended order, and previously applied patches are correctly recognized, reducing potential update errors.
Consistency and Organization: Facilitates clear organization and sequencing for patches, benefiting both developers and users.
Improved Maintenance: Supports an efficient update process by enabling easy identification and application of patches.
Thank you for considering this proposal. Please reach out if there are any questions or if additional details are needed!
The text was updated successfully, but these errors were encountered: