MySQL高可用方案MHA線上切換的步驟及原理

来源:http://www.cnblogs.com/ivictor/archive/2017/05/22/6693968.html
-Advertisement-
Play Games

在日常工作中，會碰到如下的場景，如mysql資料庫升級，主伺服器硬體升級等，這個時候就需要將寫操作切換到另外一臺伺服器上，那麼如何進行線上切換呢？同時，要求切換過程短，對業務的影響比較小。 MHA就提供了這樣一種優雅的方式，只會堵塞業務0.5~2s的時間，在這段時間內，業務無法讀取和寫入。 集群信息 ...


在日常工作中，會碰到如下的場景，如mysql資料庫升級，主伺服器硬體升級等，這個時候就需要將寫操作切換到另外一臺伺服器上，那麼如何進行線上切換呢？同時，要求切換過程短，對業務的影響比較小。

MHA就提供了這樣一種優雅的方式，只會堵塞業務0.5~2s的時間，在這段時間內，業務無法讀取和寫入。

 

集群信息

角色                             IP地址                 ServerID      類型

Master                         192.168.244.10   1                 寫入

Candicate master          192.168.244.20   2                 讀

Slave                           192.168.244.30   3                 讀

Monitor host                 192.168.244.40                      監控集群組

 

MHA具體的搭建步驟和原理，可參考另外一篇博客：

MySQL高可用方案MHA的部署和原理

 

線上切換的步驟

1. 關閉MHA監控

# masterha_stop --conf=/etc/masterha/app1.cnf

2. 線上切換

# /usr/local/bin/masterha_master_switch --conf=/etc/masterha/app1.cnf --master_state=alive --new_master_host=192.168.244.20 --new_master_port=3306 --orig_master_is_new_slave --running_updates_limit=10000

其中，

--orig_master_is_new_slave是將原master切換為新主的slave，預設情況下，是不添加的。

--running_updates_limit預設為1s，即如果主從延遲時間（Seconds_Behind_Master），或master show processlist中dml操作大於1s，則不會執行切換。

 

線上切換的輸出

Tue Apr 11 15:28:32 2017 - [info] MHA::MasterRotate version 0.56.
Tue Apr 11 15:28:32 2017 - [info] Starting online master switch..
Tue Apr 11 15:28:32 2017 - [info] 
Tue Apr 11 15:28:32 2017 - [info] * Phase 1: Configuration Check Phase..
Tue Apr 11 15:28:32 2017 - [info] 
Tue Apr 11 15:28:32 2017 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Apr 11 15:28:32 2017 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Tue Apr 11 15:28:32 2017 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Tue Apr 11 15:28:34 2017 - [info] GTID failover mode = 0
Tue Apr 11 15:28:34 2017 - [info] Current Alive Master: 192.168.244.10(192.168.244.10:3306)
Tue Apr 11 15:28:34 2017 - [info] Alive Slaves:
Tue Apr 11 15:28:34 2017 - [info]   192.168.244.20(192.168.244.20:3306)  Version=5.6.31-log (oldest major version between slaves) log
-bin:enabledTue Apr 11 15:28:34 2017 - [info]     Replicating from 192.168.244.10(192.168.244.10:3306)
Tue Apr 11 15:28:34 2017 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Apr 11 15:28:34 2017 - [info]   192.168.244.30(192.168.244.30:3306)  Version=5.6.31-log (oldest major version between slaves) log
-bin:enabledTue Apr 11 15:28:34 2017 - [info]     Replicating from 192.168.244.10(192.168.244.10:3306)

It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.244.10(192.168
.244.10:3306)? (YES/no): yes
Tue Apr 11 15:28:47 2017 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
Tue Apr 11 15:28:47 2017 - [info]  ok.
Tue Apr 11 15:28:47 2017 - [info] Checking MHA is not monitoring or doing failover..
Tue Apr 11 15:28:47 2017 - [info] Checking replication health on 192.168.244.20..
Tue Apr 11 15:28:47 2017 - [info]  ok.
Tue Apr 11 15:28:47 2017 - [info] Checking replication health on 192.168.244.30..
Tue Apr 11 15:28:47 2017 - [info]  ok.
Tue Apr 11 15:28:47 2017 - [info] 192.168.244.20 can be new master.
Tue Apr 11 15:28:47 2017 - [info] 
From:
192.168.244.10(192.168.244.10:3306) (current master)
 +--192.168.244.20(192.168.244.20:3306)
 +--192.168.244.30(192.168.244.30:3306)

To:
192.168.244.20(192.168.244.20:3306) (new master)
 +--192.168.244.30(192.168.244.30:3306)
 +--192.168.244.10(192.168.244.10:3306)

Starting master switch from 192.168.244.10(192.168.244.10:3306) to 192.168.244.20(192.168.244.20:3306)? (yes/NO): yes
Tue Apr 11 15:29:00 2017 - [info] Checking whether 192.168.244.20(192.168.244.20:3306) is ok for the new master..
Tue Apr 11 15:29:00 2017 - [info]  ok.
Tue Apr 11 15:29:00 2017 - [info] 192.168.244.10(192.168.244.10:3306): SHOW SLAVE STATUS returned empty result. To check replication 
filtering rules, temporarily executing CHANGE MASTER to a dummy host.Tue Apr 11 15:29:00 2017 - [info] 192.168.244.10(192.168.244.10:3306): Resetting slave pointing to the dummy host.
Tue Apr 11 15:29:00 2017 - [info] ** Phase 1: Configuration Check Phase completed.
Tue Apr 11 15:29:00 2017 - [info] 
Tue Apr 11 15:29:00 2017 - [info] * Phase 2: Rejecting updates Phase..
Tue Apr 11 15:29:00 2017 - [info] 
Tue Apr 11 15:29:00 2017 - [info] Executing master ip online change script to disable write on the current master:
Tue Apr 11 15:29:00 2017 - [info]   /usr/local/bin/master_ip_online_change --command=stop --orig_master_host=192.168.244.10 --orig_ma
ster_ip=192.168.244.10 --orig_master_port=3306 --orig_master_user='monitor' --orig_master_password='monitor123' --new_master_host=192.168.244.20 --new_master_ip=192.168.244.20 --new_master_port=3306 --new_master_user='monitor' --new_master_password='monitor123' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slaveTue Apr 11 15:29:00 2017 476501 Set read_only on the new master.. ok.
Tue Apr 11 15:29:00 2017 911951 Set read_only=1 on the orig master.. ok.
Tue Apr 11 15:29:00 2017 919517 Killing all application threads..
Tue Apr 11 15:29:00 2017 919552 done.
Disabling the VIP an old master: 192.168.244.10 
SIOCSIFFLAGS: Cannot assign requested address
Tue Apr 11 15:29:00 2017 - [info]  ok.
Tue Apr 11 15:29:00 2017 - [info] Locking all tables on the orig master to reject updates from everybody (including root):
Tue Apr 11 15:29:00 2017 - [info] Executing FLUSH TABLES WITH READ LOCK..
Tue Apr 11 15:29:00 2017 - [info]  ok.
Tue Apr 11 15:29:00 2017 - [info] Orig master binlog:pos is mysql-bin.000016:211.
Tue Apr 11 15:29:00 2017 - [info]  Waiting to execute all relay logs on 192.168.244.20(192.168.244.20:3306)..
Tue Apr 11 15:29:01 2017 - [info]  master_pos_wait(mysql-bin.000016:211) completed on 192.168.244.20(192.168.244.20:3306). Executed 0
 events.Tue Apr 11 15:29:01 2017 - [info]   done.
Tue Apr 11 15:29:01 2017 - [info] Getting new master's binlog name and position..
Tue Apr 11 15:29:01 2017 - [info]  mysql-bin.000009:211
Tue Apr 11 15:29:01 2017 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_
HOST='192.168.244.20', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000009', MASTER_LOG_POS=211, MASTER_USER='repl', MASTER_PASSWORD='xxx';Tue Apr 11 15:29:01 2017 - [info] Executing master ip online change script to allow write on the new master:
Tue Apr 11 15:29:01 2017 - [info]   /usr/local/bin/master_ip_online_change --command=start --orig_master_host=192.168.244.10 --orig_m
aster_ip=192.168.244.10 --orig_master_port=3306 --orig_master_user='monitor' --orig_master_password='monitor123' --new_master_host=192.168.244.20 --new_master_ip=192.168.244.20 --new_master_port=3306 --new_master_user='monitor' --new_master_password='monitor123' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slaveTue Apr 11 15:29:01 2017 109040 Set read_only=0 on the new master.
Enabling the VIP 192.168.244.188 on the new master: 192.168.244.20 
Tue Apr 11 15:29:01 2017 - [info]  ok.
Tue Apr 11 15:29:01 2017 - [info] 
Tue Apr 11 15:29:01 2017 - [info] * Switching slaves in parallel..
Tue Apr 11 15:29:01 2017 - [info] 
Tue Apr 11 15:29:01 2017 - [info] -- Slave switch on host 192.168.244.30(192.168.244.30:3306) started, pid: 17651
Tue Apr 11 15:29:01 2017 - [info] 
Tue Apr 11 15:29:02 2017 - [info] Log messages from 192.168.244.30 ...
Tue Apr 11 15:29:02 2017 - [info] 
Tue Apr 11 15:29:01 2017 - [info]  Waiting to execute all relay logs on 192.168.244.30(192.168.244.30:3306)..
Tue Apr 11 15:29:01 2017 - [info]  master_pos_wait(mysql-bin.000016:211) completed on 192.168.244.30(192.168.244.30:3306). Executed 0
 events.Tue Apr 11 15:29:01 2017 - [info]   done.
Tue Apr 11 15:29:01 2017 - [info]  Resetting slave 192.168.244.30(192.168.244.30:3306) and starting replication from the new master 1
92.168.244.20(192.168.244.20:3306)..Tue Apr 11 15:29:01 2017 - [info]  Executed CHANGE MASTER.
Tue Apr 11 15:29:01 2017 - [info]  Slave started.
Tue Apr 11 15:29:02 2017 - [info] End of log messages from 192.168.244.30 ...
Tue Apr 11 15:29:02 2017 - [info] 
Tue Apr 11 15:29:02 2017 - [info] -- Slave switch on host 192.168.244.30(192.168.244.30:3306) succeeded.
Tue Apr 11 15:29:02 2017 - [info] Unlocking all tables on the orig master:
Tue Apr 11 15:29:02 2017 - [info] Executing UNLOCK TABLES..
Tue Apr 11 15:29:02 2017 - [info]  ok.
Tue Apr 11 15:29:02 2017 - [info] Starting orig master as a new slave..
Tue Apr 11 15:29:02 2017 - [info]  Resetting slave 192.168.244.10(192.168.244.10:3306) and starting replication from the new master 1
92.168.244.20(192.168.244.20:3306)..Tue Apr 11 15:29:02 2017 - [info]  Executed CHANGE MASTER.
Tue Apr 11 15:29:02 2017 - [info]  Slave started.
Tue Apr 11 15:29:02 2017 - [info] All new slave servers switched successfully.
Tue Apr 11 15:29:02 2017 - [info] 
Tue Apr 11 15:29:02 2017 - [info] * Phase 5: New master cleanup phase..
Tue Apr 11 15:29:02 2017 - [info] 
Tue Apr 11 15:29:02 2017 - [info]  192.168.244.20: Resetting slave info succeeded.
Tue Apr 11 15:29:02 2017 - [info] Switching master to 192.168.244.20(192.168.244.20:3306) completed successfully.

 

MHA線上切換的原理

1. 檢查當前的配置信息及主從伺服器的信息

    包括讀取MHA的配置文件/etc/masterha/app1.cnf及檢查當前slave的健康狀態

2. 阻止對當前master的更新

   主要通過如下步驟：

   1> 等待1.5s（$time_until_kill_threads*100ms），等待當前連接斷開。

   2> 執行 read_only=1，阻止新的DML操作

   3> 等待0.5s，等待當前DML操作完成。

   4> kill掉所有連接。

   5> FLUSH NO_WRITE_TO_BINLOG TABLES

   6> FLUSH TABLES WITH READ LOCK

3. 等待新master執行完所有的relay log

Waiting to execute all relay logs on 192.168.244.20(192.168.244.20:3306)..

4. 將新master的read_only設置為off，並添加VIP

5. slave切換到新master上。

   1> 等待slave（192.168.244.30）應用完原主從複製產生的relay log，然後執行change master操作切換到新master上。

   2> 釋放原master上加的鎖。

   3> 因masterha_master_switch命令行中帶有--orig_master_is_new_slave參數，故原master也切換為新master的從。

6. 清理新master的相關信息。

    主要是執行了reset slave all操作，清除之前的複製信息。

 

MHA線上切換需滿足的條件

MHA在執行線上切換之前，會判斷當前的主從複製信息，只有滿足了以下條件，才能執行切換動作：

1. 所有SLAVE的IO線程和SQL線程都在運行。

2. 所有slave的Seconds_Behind_Master小於或等於running_updates_limit的值，該參數如果沒有顯示指定的話，則預設為1s

3. 在master上，通過show processlist輸出，沒有一個DML操作的時間大於running_updates_limit的值。

 

線上切換時，打開general log，各個伺服器的操作信息

註：在執行masterha_master_switch命令時，會有兩次確認操作

1. It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.244.10(192.168
.244.10:3306)? (YES/no):

2. Starting master switch from 192.168.244.10(192.168.244.10:3306) to 192.168.244.20(192.168.244.20:3306)? (yes/NO):

以下輸出中間都有兩次空白，其中第一次空白之前的輸出對應第一次確認之前，第二次之前的輸出對應第二次確認之前。

 

原master 192.168.244.10

170412 16:52:38    23 Connect    monitor@node4 on 
                   23 Query    set autocommit=1
                   23 Query    SELECT CONNECTION_ID() AS Value
170412 16:52:39    24 Connect    monitor@node4 on 
                   24 Query    set autocommit=1
                   24 Query    SELECT CONNECTION_ID() AS Value
                   24 Query    SET wait_timeout=86400
                   24 Query    SELECT @@global.server_id As Value
                   24 Query    SELECT VERSION() AS Value
                   24 Query    SELECT @@global.gtid_mode As Value
                   24 Query    SHOW GLOBAL VARIABLES LIKE 'log_bin'
                   24 Query    SHOW MASTER STATUS
                   24 Query    SELECT @@global.datadir AS Value
                   24 Query    SELECT @@global.slave_parallel_workers AS Value
                   24 Query    SHOW SLAVE STATUS
                   24 Query    SELECT @@global.read_only As Value
                   24 Query    SELECT @@global.relay_log_purge As Value

           
170412 16:54:06    24 Query    FLUSH NO_WRITE_TO_BINLOG TABLES
                   24 Query    SELECT GET_LOCK('MHA_Master_High_Availability_Monitor', '0') AS Value
                   24 Query    SHOW PROCESSLIST
                   

170412 16:55:51    24 Query    SHOW SLAVE STATUS
                   24 Query    CHANGE MASTER TO MASTER_HOST='dummy_host'
170412 16:55:52    24 Query    SHOW SLAVE STATUS
                   24 Query    RESET SLAVE /*!50516 ALL */
                   24 Query    SELECT RELEASE_LOCK('MHA_Master_High_Availability_Monitor') As Value
                   24 Quit    
                   25 Connect    monitor@node4 on 
                   25 Query    set autocommit=1
                   25 Query    SELECT CONNECTION_ID() AS Value
                   25 Query    SET sql_log_bin=0
                   25 Query    SHOW PROCESSLIST
                   25 Query    SELECT @@global.read_only As Value
                   25 Query    SET GLOBAL read_only=1
                   25 Query    SELECT @@global.read_only As Value
                   25 Query    SHOW PROCESSLIST
                   25 Query    SET sql_log_bin=1
                   25 Quit    
                   26 Connect    monitor@node4 on 
                   26 Query    set autocommit=1
                   26 Query    SELECT CONNECTION_ID() AS Value
                   26 Query    SET wait_timeout=86400
                   26 Query    FLUSH TABLES WITH READ LOCK
                   26 Query    SHOW MASTER STATUS
170412 16:55:53    26 Query    UNLOCK TABLES
                   26 Query    CHANGE MASTER TO MASTER_HOST = '192.168.244.20' MASTER_USER = 'repl' MASTER_PASSWORD = <secret> MASTE
R_PORT = 3306 MASTER_LOG_FILE = 'mysql-bin.000010' MASTER_LOG_POS = 120           26 Query    SET GLOBAL relay_log_purge=0
                   26 Query    START SLAVE
                   27 Connect Out    repl@192.168.244.20:3306
                   26 Query    SHOW SLAVE STATUS
                   26 Query    SELECT RELEASE_LOCK('MHA_Master_High_Availability_Failover') As Value
                   26 Quit

 

新master 192.168.244.20

170412 16:52:38    23 Connect    monitor@node4 on 
                   23 Query    set autocommit=1
                   23 Query    SELECT CONNECTION_ID() AS Value
170412 16:52:39    24 Connect    monitor@node4 on 
                   24 Query    set autocommit=1
                   24 Query    SELECT CONNECTION_ID() AS Value
                   24 Query    SET wait_timeout=86400
                   24 Query    SELECT @@global.server_id As Value
                   24 Query    SELECT VERSION() AS Value
                   24 Query    SELECT @@global.gtid_mode As Value
                   24 Query    SHOW GLOBAL VARIABLES LIKE 'log_bin'
                   24 Query    SHOW MASTER STATUS
                   24 Query    SELECT @@global.datadir AS Value
                   24 Query    SELECT @@global.slave_parallel_workers AS Value
                   24 Query    SHOW SLAVE STATUS
                   24 Query    SELECT @@global.read_only As Value
                   24 Query    SELECT @@global.relay_log_purge As Value
                   24 Query    SELECT @@global.relay_log_info_repository AS Value
                   24 Query    SELECT @@global.datadir AS Value
                   24 Query    SELECT @@global.relay_log_info_file AS Value
                   24 Query    SHOW SLAVE STATUS
                   24 Query    SELECT Repl_slave_priv AS Value FROM mysql.user WHERE user = 'repl'

           
           
170412 16:54:06    24 Query    SELECT GET_LOCK('MHA_Master_High_Availability_Failover', '0') AS Value
                   24 Query    SHOW SLAVE STATUS
                   24 Query    SHOW SLAVE STATUS

           
170412 16:55:52    24 Query    SHOW PROCESSLIST
                   25 Connect    monitor@node4 on 
                   25 Query    set autocommit=1
                   25 Query    SELECT CONNECTION_ID() AS Value
                   25 Query    SELECT @@global.read_only As Value
                   25 Query    SELECT @@global.read_only As Value
                   25 Quit    
                   24 Query    SHOW SLAVE STATUS
                   24 Query    SELECT MASTER_POS_WAIT('mysql-bin.000017','120',0) AS Result
                   24 Query    STOP SLAVE SQL_THREAD
                   24 Query    SHOW SLAVE STATUS
                   24 Query    SHOW MASTER STATUS
                   26 Connect    monitor@node4 on 
                   26 Query    set autocommit=1
                   26 Query    SELECT CONNECTION_ID() AS Value
                   26 Query    SET sql_log_bin=0
                   26 Query    SELECT @@global.read_only As Value
                   26 Query    SET GLOBAL read_only=0
                   26 Query    SET sql_log_bin=1
                   26 Quit    
                   24 Query    SELECT @@global.read_only As Value
                   27 Connect    repl@node3 on 
                   27 Query    SELECT UNIX_TIMESTAMP()
                   27 Query    SHOW VARIABLES LIKE 'SERVER_ID'
                   27 Query    SET @master_heartbeat_period= 1799999979520
                   27 Query    SET @master_binlog_checksum= @@global.binlog_checksum
                   27 Query    SELECT @master_binlog_checksum
                   27 Query    SELECT @@GLOBAL.GTID_MODE
                   27 Query    SHOW VARIABLES LIKE 'SERVER_UUID'
                   27 Query    SET @slave_uuid= '8a1093c8-1d00-11e7-954f-000c299a5715'
                   27 Binlog Dump    Log: 'mysql-bin.000010'  Pos: 120
170412 16:55:53    28 Connect    repl@node1 on 
                   28 Query    SELECT UNIX_TIMESTAMP()
                   28 Query    SHOW VARIABLES LIKE 'SERVER_ID'
                   28 Query    SET @master_heartbeat_period= 1799999979520
                   28 Query    SET @master_binlog_checksum= @@global.binlog_checksum
                   28 Query    SELECT @master_binlog_checksum
                   28 Query    SELECT @@GLOBAL.GTID_MODE
                   28 Query    SHOW VARIABLES LIKE 'SERVER_UUID'
                   24 Query    STOP SLAVE
                   28 Query    SET @slave_uuid= '2a6365e0-1d05-11e7-956d-000c29c64704'
                   28 Binlog Dump    Log: 'mysql-bin.000010'  Pos: 120
                   24 Query    SHOW SLAVE STATUS
                   24 Query    RESET SLAVE /*!50516 ALL */
                   24 Query    SHOW SLAVE STATUS
                   24 Query    SELECT RELEASE_LOCK('MHA_Master_High_Availability_Failover') As Value
                   24 Quit

 

slave 192.168.244.30

170412 16:52:37    16 Connect    monitor@node4 on 
                   16 Query    set autocommit=1
                   16 Query    SELECT CONNECTION_ID() AS Value
170412 16:52:38
您的分享是我們最大的動力!

-Advertisement-
Play Games
更多相關文章
  • javascript知識整理之this
    js中的this是一個頭疼的問題，尤其對於筆者這種初級的菜鳥來講，下麵梳理下this的知識，可以當做是初級進階也好入門也罷，總歸輸出的才是自己掌握的: Js中this不是由詞法作用域決定的 而是調用時動態指定，這就有點麻煩了，如果不能明確知道函數調用時的詞法作用域this的指向也就只能靠猜了，算一卦 ...
  • React配合Webpack實現代碼分割與非同步載入
    這是Webpack+React系列配置過程記錄的第四篇。其他內容請參考： 第一篇：使用webpack、babel、react、antdesign配置單頁面應用開發環境 第二篇：使用react-router實現單頁面應用路由 第三篇：優化單頁面開發環境：webpack與react的運行時打包與熱更新 ...
  • 網頁CSS中*{margin:0; padding:0;}有什麼用
    * 這東西叫“通配符”用來匹配頁面上所有元素。*{margin:0; padding:0;} 像 2L 所說，body ,ul, li ,p,h1~h6,dd,dt 等……都有預設的margin 或padding值的，加上這句就可以刪除瀏覽器這些預設值，方面後面的設置。（註：不是沒它不行，只是方便而 ...
  • 淺談Kotlin（三）：類
    淺談Kotlin（一）：簡介及Android Studio中配置 淺談Kotlin（二）：基本類型、基本語法、代碼風格 前言： 已經學習了前兩篇文章，對Kotlin有了一個基本的認識，往後的文章開始深入介紹Kotlin的實戰使用。 本篇介紹Kotlin中類的使用。 一、表現形式 首先看一段Java中 ...
  • 【代碼筆記】iOS-Label隨字自動變大
    一，效果圖。 二，工程圖。 三， 代碼。 RootViewController.h #import <UIKit/UIKit.h> //添加HPGrowingTextView頭文件 #import "HPGrowingTextView.h" @interface RootViewController ...
  • Android學習筆記-ImageView(圖像視圖)
    原文來自：http://www.runoob.com/w3cnote/android-tutorial-imageview.html 本節引言： 本節介紹的UI基礎控制項是：ImageView(圖像視圖)，見名知意，就是用來顯示圖像的一個View或者說控制項！ 官方API:ImageView;本節講解的 ...
  • 導出空表表結構方法
    在導出資料庫dmp文件時，有資料庫表空記錄的情況下，該空表不會被導出表結構，應用如下格式代碼： select 'alter table ' || table_name || ' allocate extent(size 64k);' sql_text, table_name, tablespace_ ...
  • .Net程式員學用Oracle系列(28)：PLSQL 之SQL分類和動態SQL
    " 1、SQL 語句分類 " "1.1、分類方法及類型" "1.2、數據定義語言" "1.3、數據操縱語言" "1.4、其它語句" " 2、動態 SQL 理論 " "2.1、動態 SQL 的用途" "2.2、動態 SQL 的語法" "2.3、綁定變數" " 3、動態 SQL 實戰 " "3.1、封裝 ...
一周排行
    -Advertisement-
    Play Games
  • WPF 已知問題 監聽 WMI 事件導致觸摸失效
    示例項目結構 在 Visual Studio 中創建一個 WinForms 應用程式後，項目結構如下所示： MyWinFormsApp/ │ ├───Properties/ │ └───Settings.settings │ ├───bin/ │ ├───Debug/ │ └───Release/ ...
  • [STAThread]特性
    [STAThread] 特性用於需要與 COM 組件交互的應用程式，尤其是依賴單線程模型（如 Windows Forms 應用程式）的組件。在 STA 模式下，線程擁有自己的消息迴圈，這對於處理用戶界面和某些 COM 組件是必要的。 [STAThread] static void Main(stri ...
  • UWP WinUI3 傳入 AddHandler 的 RoutedEventHandler 類型與事件所需不匹配將拋出參數異常
    在WinForm中使用全局異常捕獲處理 在WinForm應用程式中，全局異常捕獲是確保程式穩定性的關鍵。通過在Program類的Main方法中設置全局異常處理，可以有效地捕獲並處理未預見的異常，從而避免程式崩潰。 註冊全局異常事件 [STAThread] static void Main() { / ...
  • .NET 多版本 WinForm 開源控制項庫 SunnyUI
    前言 給大家推薦一款開源的 Winform 控制項庫，可以幫助我們開發更加美觀、漂亮的 WinForm 界面。 項目介紹 SunnyUI.NET 是一個基於 .NET Framework 4.0+、.NET 6、.NET 7 和 .NET 8 的 WinForm 開源控制項庫，同時也提供了工具類庫、擴展 ...
  • .net core8 使用Swagger（附當前源碼）
    說明 該文章是屬於OverallAuth2.0系列文章，每周更新一篇該系列文章（從0到1完成系統開發）。 該系統文章，我會儘量說的非常詳細，做到不管新手、老手都能看懂。 說明：OverallAuth2.0 是一個簡單、易懂、功能強大的許可權+可視化流程管理系統。 有興趣的朋友，請關註我吧(*^▽^*) ...
  • WPF 什麼時候 VisualTreeHelper.GetDescendantBounds 將返回無窮大
    一、下載安裝 1.下載git 必須先下載並安裝git，再TortoiseGit下載安裝 git安裝參考教程：https://blog.csdn.net/mukes/article/details/115693833 2.TortoiseGit下載與安裝 TortoiseGit，Git客戶端，32/6 ...
  • C# 開源教程帶你輕鬆掌握數據結構與演算法
    前言 在項目開發過程中，理解數據結構和演算法如同掌握蓋房子的秘訣。演算法不僅能幫助我們編寫高效、優質的代碼，還能解決項目中遇到的各種難題。 給大家推薦一個支持C#的開源免費、新手友好的數據結構與演算法入門教程：Hello演算法。 項目介紹 《Hello Algo》是一本開源免費、新手友好的數據結構與演算法入門 ...
  • 第22篇 生成proto文件bat腳本
    1.生成單個Proto.bat內容 @rem Copyright 2016, Google Inc. @rem All rights reserved. @rem @rem Redistribution and use in source and binary forms, with or with ...
  • 記一次 .NET某上位機視覺程式 卡死分析
    一：背景 1. 講故事 前段時間有位朋友找到我，說他的窗體程式在客戶這邊出現了卡死，讓我幫忙看下怎麼回事？dump也生成了，既然有dump了那就上 windbg 分析吧。 二：WinDbg 分析 1. 為什麼會卡死 窗體程式的卡死，入口門檻很低，後續往下分析就不一定了，不管怎麼說先用 !clrsta ...
  • 醫學DICOM文件與PACS系統進行數據傳輸
    前言 人工智慧時代，人臉識別技術已成為安全驗證、身份識別和用戶交互的關鍵工具。 給大家推薦一款.NET 開源提供了強大的人臉識別 API，工具不僅易於集成，還具備高效處理能力。 本文將介紹一款如何利用這些API，為我們的項目添加智能識別的亮點。 項目介紹 GitHub 上擁有 1.2k 星標的 C# ...
所有分類