Migrate database to UTF-8 collation and update project documentation #39
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.
Description
This pull request includes several changes to modernize the database setup, improve compatibility, and reflect the current state of the project:
Update Database Collation:
Latin1_General_100_CS_AS_SC_UTF8
collation, requiring MSSQL 2019 as the minimum supported version.SQL_Latin1_General_CP1_CI_AS
by modifying theimport.ps1
script. Note that UTF-8 compatibility is necessary for proper functionality.Adjust
VERSION
Table:VERSION
table to match recent changes inLoginServer
.strFile
toVARCHAR
instead ofNVARCHAR
due to the new UTF-8-compatible collation.Update Documentation:
README.md
file to reflect the current state of the project and provide accurate setup instructions.Notes