Skip to content
项目
群组
代码片段
帮助
正在加载...
帮助
为 GitLab 提交贡献
登录/注册
切换导航
H
h2database
项目
项目
详情
活动
周期分析
仓库
仓库
文件
提交
分支
标签
贡献者
分枝图
比较
统计图
议题
0
议题
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
CI / CD
CI / CD
流水线
作业
计划
统计图
Wiki
Wiki
代码片段
代码片段
成员
成员
折叠边栏
关闭边栏
活动
分枝图
统计图
创建新议题
作业
提交
议题看板
打开侧边栏
Administrator
h2database
Commits
bba0bbb6
提交
bba0bbb6
authored
16 年前
作者:
Thomas Mueller
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Improve LOCK_MODE documentation.
上级
1dcac826
无相关合并请求
显示空白字符变更
内嵌
并排
正在显示
2 个修改的文件
包含
21 行增加
和
7 行删除
+21
-7
JdbcConnection.java
h2/src/main/org/h2/jdbc/JdbcConnection.java
+14
-2
help.csv
h2/src/main/org/h2/res/help.csv
+7
-5
没有找到文件。
h2/src/main/org/h2/jdbc/JdbcConnection.java
浏览文件 @
bba0bbb6
...
...
@@ -591,9 +591,21 @@ public class JdbcConnection extends TraceObject implements Connection {
/**
* Changes the current transaction isolation level. Calling this method will
* commit an open transaction, even if the new level is the same as the old
* one, except if the level is not supported.
* one, except if the level is not supported. Internally, this method calls
* SET LOCK_MODE. The following isolation levels are supported:
* <ul>
* <li> Connection.TRANSACTION_READ_UNCOMMITTED = SET LOCK_MODE 0: No
* locking (should only be used for testing). </li>
* <li>Connection.TRANSACTION_SERIALIZABLE = SET LOCK_MODE 1: Table level
* locking. </li>
* <li>Connection.TRANSACTION_READ_COMMITTED = SET LOCK_MODE 3: Table
* level locking, but read locks are released immediately (default). </li>
* </ul>
* This setting is not persistent. Please note that using
* TRANSACTION_READ_UNCOMMITTED while at the same time using multiple
* connections may result in inconsistent transactions.
*
* @param level the new transaction isolation level
,
* @param level the new transaction isolation level
:
* Connection.TRANSACTION_READ_UNCOMMITTED,
* Connection.TRANSACTION_READ_COMMITTED, or
* Connection.TRANSACTION_SERIALIZABLE
...
...
This diff is collapsed.
Click to expand it.
h2/src/main/org/h2/res/help.csv
浏览文件 @
bba0bbb6
...
...
@@ -912,14 +912,16 @@ SET LOCK_MODE int
","
Sets the lock mode.
0: No locking (should only be used for testing). Also known as READ_UNCOMMITTED.
1: Table level locking
(default)
. Also known as SERIALIZABLE.
1: Table level locking. Also known as SERIALIZABLE.
2: Table level locking with garbage collection (if the application does not close all connections).
3: Table level locking, but read locks are released immediately. Also known as READ_COMMITTED.
3: Table level locking, but read locks are released immediately
(default)
. Also known as READ_COMMITTED.
This setting is not persistent.
Please note that using SET LOCK_MODE 0 while at the same time using multiple
connections may result in inconsistent transactions.
Admin rights are required to execute this command.
This setting can be appended to the database URL: jdbc:h2:test;LOCK_MODE=3
","
SET LOCK_MODE
2
SET LOCK_MODE
1
"
"Commands (Other)","SET LOCK_TIMEOUT","
...
...
@@ -2967,7 +2969,7 @@ Returns the name of the current user of this session.
CURRENT_USER()
"
"System
tables","Information s
chema","
"System
Tables","Information S
chema","
INFORMATION_SCHEMA
","
To get the list of system tables, execute the statement
...
...
@@ -2976,7 +2978,7 @@ WHERE TABLE_SCHEMA = 'INFORMATION_SCHEMA'
","
"
"System
tables","Range t
able","
"System
Tables","Range T
able","
SYSTEM_RANGE(start, end)
","
Contains all values from start to end (this is a dynamic table).
...
...
This diff is collapsed.
Click to expand it.
编写
预览
Markdown
格式
0%
重试
或
添加新文件
添加附件
取消
您添加了
0
人
到此讨论。请谨慎行事。
请先完成此评论的编辑!
取消
请
注册
或者
登录
后发表评论