-
-
Notifications
You must be signed in to change notification settings - Fork 539
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
[management] Add MySQL Support #3108
Conversation
* Update store.go * Update sql_store.go * Update store.go * Update golang-test-linux.yml * Update store.go * Update go.mod * Update go.mod * Update go.sum * Update store.go * Update sql_store.go * TestContainer * Update go.sum * Update store.go * TestUtil Duplicate * dsn fix * go mod tidy * NETBIRD_STORE_ENGINE_MYSQL_DSN * Skip Test * Update test-infrastructure-files.yml * Update test-infrastructure-files.yml * MYSQL_ROOT_PASSWORD added * Update test-infrastructure-files.yml * Update store.go * Debug + Mysql JSON Query * swicth/case convert * Update store.go * Update store.go * Debug * MySQL Test Version Change * Root Test * Ignore other sql tests. * MySQL Connection Fix * enable other tests * The word "key" is a reserved word in MySQL. * Remove Debugs * Update sql_store.go * Added default null value for datetime. * Added default null value for datetime. * MySQL Hooks * MySQL Config File * remove default values * test timeout change * MySQL max lifetime change * WithConfigFile * disable other tests * Update mysql.cnf * Update golang-test-linux.yml * Delete sql_hooks.go * enable other tests * test timeout change * update packets * Fix the Inactivity Expiration problem * Update sql_store.go * Update mysql.cnf * Update sql_store.go * Update sql_store.go * timeout change * MySQL Connection LifeTime Change * TestContainers have been optimized. * Update store_ios.go * Update sql_store.go * timeout fix * fix migration (setup keys) * Update event.go * Add disable option for event activities. * Revert "Update event.go" * Update event.go * Fix Gorm Mysql Bug * update go-jose module * containerd module update * containerd downgrade * Revert commits * Revert "Revert commits" This reverts commit 62b3eac. * Revert "containerd downgrade" This reverts commit 4e46108. * Revert "containerd module update" This reverts commit e8cfa87. * Revert "update go-jose module" This reverts commit 1fabdc7.
Signed-off-by: bcmmbaga <[email protected]>
# Conflicts: # management/server/account.go # management/server/store/sql_store.go # management/server/store/store.go
Signed-off-by: bcmmbaga <[email protected]>
a25e299
to
6a1db52
Compare
Signed-off-by: bcmmbaga <[email protected]>
6a1db52
to
626b36f
Compare
Signed-off-by: bcmmbaga <[email protected]>
c155d2b
to
7328a0e
Compare
Signed-off-by: bcmmbaga <[email protected]>
7328a0e
to
80d1bed
Compare
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
b7da985
to
1adab0d
Compare
Signed-off-by: bcmmbaga <[email protected]>
4c4bc16
to
525019b
Compare
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
64fa18f
to
c76683a
Compare
Signed-off-by: bcmmbaga <[email protected]>
0b9d596
to
265b042
Compare
All of these commits are unnecessary. In the PR I have already opened, mysql is running without any problems. I don't understand why you send so many useless commits. |
The current setup with MySQL works only when the SQL mode is not set, but with the default strict mode, it encounters issues. Some of the broken functionality includes adding new users, creating user PATs, creating new setup keys, and adding new peers. These additional commits aim to address these problems and ensure the MySQL test container runs in strict mode to verify everything works correctly and to catch any potential issues that could break MySQL support |
Signed-off-by: bcmmbaga <[email protected]>
dbe2d0f
to
b740fef
Compare
It should not be difficult for users to set sql mode. I have been using the mysql engine in a production environment for 1 month. I have not encountered any problems so far. 250+ onlines Performance is quite good. |
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
f517031
to
b178e71
Compare
Signed-off-by: bcmmbaga <[email protected]>
da944cb
to
a49cccf
Compare
Signed-off-by: bcmmbaga <[email protected]>
Signed-off-by: bcmmbaga <[email protected]>
Quality Gate passedIssues Measures |
Describe your changes
Issue ticket number and link
Checklist