From db9a0b9bf8501192ceda4b64a6eb9a6025502555 Mon Sep 17 00:00:00 2001 From: asdf123123123 Date: Mon, 29 Jun 2020 22:25:15 -0400 Subject: [PATCH 1/4] =?UTF-8?q?Update=20=E8=AE=BE=E8=AE=A1=E6=A8=A1?= =?UTF-8?q?=E5=BC=8F.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Added another article --- docs/system-design/设计模式.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/system-design/设计模式.md b/docs/system-design/设计模式.md index 6af52e41..3f45d85c 100644 --- a/docs/system-design/设计模式.md +++ b/docs/system-design/设计模式.md @@ -35,7 +35,7 @@ ### 常见结构型模式详解 - **适配器模式：** - - [深入理解适配器模式——加个“适配器”以便于复用](https://segmentfault.com/a/1190000011856448) + - [深入理解适配器模式——加个“适配器”以便于复用](https://segmentfault.com/a/1190000011856448) https://blog.csdn.net/carson_ho/article/details/54910430 - [适配器模式原理及实例介绍-IBM](https://www.ibm.com/developerworks/cn/java/j-lo-adapter-pattern/index.html) - **桥接模式：** [设计模式笔记16：桥接模式(Bridge Pattern)](https://blog.csdn.net/yangzl2008/article/details/7670996) - **组合模式：** [大话设计模式—组合模式](https://blog.csdn.net/lmb55/article/details/51039781) From c3df908b173534bb97975d410b4965718e911e9c Mon Sep 17 00:00:00 2001 From: "jianxin.yuan" <53457400+jianxin-yuan@users.noreply.github.com> Date: Tue, 30 Jun 2020 22:54:38 +0800 Subject: [PATCH 2/4] =?UTF-8?q?=E6=96=B0=E5=A2=9E=20"=E5=8F=AF=E4=BD=9C?= =?UTF-8?q?=E4=B8=BAGC=20Roots=20=E7=9A=84=E5=AF=B9=E8=B1=A1"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/java/jvm/JVM垃圾回收.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/java/jvm/JVM垃圾回收.md b/docs/java/jvm/JVM垃圾回收.md index 7fa344ce..028b3750 100644 --- a/docs/java/jvm/JVM垃圾回收.md +++ b/docs/java/jvm/JVM垃圾回收.md @@ -238,6 +238,11 @@ public class ReferenceCountingGc { ![可达性分析算法 ](./pictures/jvm垃圾回收/72762049.png) +可作为GC Roots的对象包括下面几种: +* 虚拟机栈(栈帧中的本地变量表)中引用的对象 +* 本地方法栈(Native方法)中引用的对象 +* 方法区中类静态属性引用的对象 +* 方法区中常量引用的对象 ### 2.3 再谈引用 From e0c0abb5832b7e41e3fab8b659d1b32b1a57b74a Mon Sep 17 00:00:00 2001 From: liwenguang Date: Sat, 4 Jul 2020 16:08:39 +0800 Subject: [PATCH 3/4] fix843 --- docs/database/MySQL.md | 2 +- docs/system-design/framework/spring/spring-transaction.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/database/MySQL.md b/docs/database/MySQL.md index 8e74cb89..8fd54b7d 100644 --- a/docs/database/MySQL.md +++ b/docs/database/MySQL.md @@ -199,7 +199,7 @@ select sql_no_cache count(*) from usr; | REPEATABLE-READ | × | × | √ | | SERIALIZABLE | × | × | × | -MySQL InnoDB 存储引擎的默认支持的隔离级别是 **REPEATABLE-READ（可重读）**。我们可以通过`SELECT @@tx_isolation;`命令来查看 +MySQL InnoDB 存储引擎的默认支持的隔离级别是 **REPEATABLE-READ（可重读）**。我们可以通过`SELECT @@tx_isolation;`命令来查看，MySQL 8.0 该命令改为`SELECT @@transaction_isolation;` ```sql mysql> SELECT @@tx_isolation; diff --git a/docs/system-design/framework/spring/spring-transaction.md b/docs/system-design/framework/spring/spring-transaction.md index 6eafb10b..38099337 100644 --- a/docs/system-design/framework/spring/spring-transaction.md +++ b/docs/system-design/framework/spring/spring-transaction.md @@ -484,7 +484,7 @@ public enum Isolation { 因为平时使用 MySQL 数据库比较多，这里再多提一嘴！ -MySQL InnoDB 存储引擎的默认支持的隔离级别是 **`REPEATABLE-READ`（可重读）**。我们可以通过`SELECT @@tx_isolation;`命令来查看，如下： +MySQL InnoDB 存储引擎的默认支持的隔离级别是 **`REPEATABLE-READ`（可重读）**。我们可以通过`SELECT @@tx_isolation;`命令来查看，MySQL 8.0 该命令改为`SELECT @@transaction_isolation;`： ``` mysql> SELECT @@tx_isolation; From ff0174c54675550ea49751930fdccd1e4b949edf Mon Sep 17 00:00:00 2001 From: asdf123123123 Date: Sun, 5 Jul 2020 13:04:46 -0400 Subject: [PATCH 4/4] =?UTF-8?q?Update=20=E8=AE=BE=E8=AE=A1=E6=A8=A1?= =?UTF-8?q?=E5=BC=8F.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 加入迭代器模式参考文章 --- docs/system-design/设计模式.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/system-design/设计模式.md b/docs/system-design/设计模式.md index 3f45d85c..c7a86716 100644 --- a/docs/system-design/设计模式.md +++ b/docs/system-design/设计模式.md @@ -68,7 +68,7 @@ - [责任链模式实现的三种方式](https://www.cnblogs.com/lizo/p/7503862.html) - **命令模式：** 在软件设计中，我们经常需要向某些对象发送请求，但是并不知道请求的接收者是谁，也不知道被请求的操作是哪个，我们只需在程序运行时指定具体的请求接收者即可，此时，可以使用命令模式来进行设计，使得请求发送者与请求接收者消除彼此之间的耦合，让对象之间的调用关系更加灵活。命令模式可以对发送者和接收者完全解耦，发送者与接收者之间没有直接引用关系，发送请求的对象只需要知道如何发送请求，而不必知道如何完成请求。这就是命令模式的模式动机。 - **解释器模式：** -- **迭代器模式：** +- **迭代器模式：** - **中介者模式：** - **备忘录模式：** - **观察者模式：** 、