Mybatis 3.3.0 中文用户指南
| LOG4J | LOG4J2 | JDK_LOGGING | Not set Save web pages as PDF manually or automatically with PDFmyURL 未指定时将自动查 找。 JDK_LOGGING | COMMONS_LOGGING | STDOUT_LOGGING | NO_LOGGING proxyFactory 指定 Mybatis 日志 日志 项目文档 项目文档 项目文档 项目文档 项目信息 项目信息 项目报表 项目报表 Logging Mybatis内置的日志工厂提供日志功能,具体的日志实现有以下几种工具: SLF4J Apache Commons Logging Log4j 2 Log4j JDK logging 具体选择哪个日志实现工具由MyBatis的内置日志工厂确定。它会使用最先找到的(按上文列举的顺序查找)。 含Commons Logging,如Tomcat和WebShpere, 所以MyBatis会把它作为具体的日志实 现。记住这点非常重要。这将意味着,在诸如 WebSphere的环境中——WebSphere提供了Commons Logging的私有实现,你的 Log4J配置将被忽略。 这种做法不免让人悲催,MyBatis怎么能忽略你的配置呢?事实上,因Commons Logging已经存 在了,按照0 码力 | 98 页 | 2.03 MB | 1 年前3MySQL Installer Guide
...................................................................................... 14 4.1.6 Logging Options ........................................................................................ ...................................................................................... 14 4.1.6 Logging Options ........................................................................................ be added and configured in MySQL Workbench. • Checking Show Advanced Options enables additional Logging Options to be set. This includes defining custom file paths for the error log, general log, slow0 码力 | 42 页 | 448.90 KB | 1 年前3Apache Cassandra™ 10 Documentation February 16, 2012
Configuration 84 access.properties 84 passwd.properties 85 Logging Configuration 85 Logging Levels via the Properties File 85 Logging Levels via JMX 85 Operations 86 Monitoring a Cassandra Cluster c. Save and close the file. d. Source the file. source $HOME/.bashrc 5. Create the data and logging directory for Cassandra. $ mkdir $HOME/datastax/cassandra-data Configuring and Starting a Single-Node location>/export PATH=$PATH:$CASSANDRA_HOME/bin 3. Create the data and logging directories needed by Cassandra. By default, Cassandra uses /var/lib/cassandra and /var/log/cassandra 0 码力 | 141 页 | 2.52 MB | 1 年前3phpMyAdmin Documentation Release 5.2.2-dev
$cfg['Servers'][$i] ['pmadb']. When false, history is stored in the browser and is cleared when logging out. See also $cfg['Servers'][$i]['history'] See also $cfg['QueryHistoryDB'] PMA_QUERYHISTORYMAX advanced features are not enabled by default: they can still potentially be enabled by the user when logging in with the Zero configuration feature. Note Suggested values: phpmyadmin or pmadb See also $ o_4_3_0+.sql. Do not forget to clear the browser cache and to empty the old session by logging out and logging in again. Using authentication modes HTTP and cookie authentication modes are recommended0 码力 | 252 页 | 379.56 KB | 1 年前3phpMyAdmin Documentation Release 5.2.2-dev
to $cfg['Servers'][$i]['pmadb']. When false, history is stored in the browser and is cleared when logging out. See also: $cfg['Servers'][$i]['history'] See also: 10 Chapter 3. Installation phpMyAdmin advanced features are not enabled by default: they can still potentially be enabled by the user when logging in with the Zero configuration feature. Note: Suggested values: phpmyadmin or pmadb See also: o_4_3_0+.sql. Do not forget to clear the browser cache and to empty the old session by logging out and logging in again. 3.11 Using authentication modes HTTP and cookie authentication modes are recommended0 码力 | 209 页 | 868.03 KB | 1 年前3phpMyAdmin Documentation Release 6.0.0-dev
to $cfg['Servers'][$i]['pmadb']. When false, history is stored in the browser and is cleared when logging out. See also: $cfg['Servers'][$i]['history'] See also: 10 Chapter 3. Installation phpMyAdmin advanced features are not enabled by default: they can still potentially be enabled by the user when logging in with the Zero configuration feature. Note: Suggested values: phpmyadmin or pmadb See also: o_4_3_0+.sql. Do not forget to clear the browser cache and to empty the old session by logging out and logging in again. 3.11 Using authentication modes HTTP and cookie authentication modes are recommended0 码力 | 209 页 | 869.53 KB | 1 年前3phpMyAdmin Documentation release 5.0.4
o_4_3_0+.sql. Do not forget to clear the browser cache and to empty the old session by logging out and logging in again. Using authentication modes HTTP and cookie authentication modes are recommended instead. Issue 11922 [https://github.com/phpmyadmin/phpmyadmin/issues/11922]. Trouble logging back in after logging out using ‘http’ authentication When using the ‘http’ auth_type, it can be impossible Type:: Default value:: Type:: Default value:: Type:: Default value:: Configure authentication logging destination. Failed (or all, depending on $cfg['AuthLogSuccess']) authentication attempts will be0 码力 | 235 页 | 370.30 KB | 1 年前3phpMyAdmin Documentation Release 5.0.5-dev
o_4_3_0+.sql. Do not forget to clear the browser cache and to empty the old session by logging out and logging in again. Using authentication modes HTTP and cookie authentication modes are recommended instead. Issue 11922 [https://github.com/phpmyadmin/phpmyadmin/issues/11922]. Trouble logging back in after logging out using ‘http’ authentication When using the ‘http’ auth_type, it can be impossible Type:: Default value:: Type:: Default value:: Type:: Default value:: Configure authentication logging destination. Failed (or all, depending on $cfg['AuthLogSuccess']) authentication attempts will be0 码力 | 235 页 | 370.31 KB | 1 年前3phpMyAdmin Documentation release 5.1.0
o_4_3_0+.sql. Do not forget to clear the browser cache and to empty the old session by logging out and logging in again. Using authentication modes HTTP and cookie authentication modes are recommended instead. Issue 11922 [https://github.com/phpmyadmin/phpmyadmin/issues/11922]. Trouble logging back in after logging out using ‘http’ authentication When using the ‘http’ auth_type, it can be impossible 'auto' New in version 4.8.0: This is supported since phpMyAdmin 4.8.0. Configure authentication logging destination. Failed (or all, depending on $cfg['AuthLogSuccess']) authentication attempts will be0 码力 | 241 页 | 370.94 KB | 1 年前3Greenplum分布式事务和两阶段提交协议
事务实现原理和Write Ahead Logging(WAL) ● 分布式事务和两阶段提交的原理 ● Greenplum两阶段提交协议的实现 ● Greenplum两阶段提交协议的优化 Outline 7 事务的属性:ACID 属性 含义 数据库系统的实现 Atomic 原子性 事务中的操作要么全部正确执行,要么完全不 执行。 Write Ahead Logging,分布式事务:两阶段提交协议 两阶段加锁(Two Phase Locking, 2PL)、乐观并发控制 (OCC) Durability 持久性 一个事务在提交之后,该事务对数据库的改变 是持久的。 Write Ahead Logging + 存储管理 Jim Gray于1981年VLDB描述了事务的原子性、一致性和持久性,在此基础上,Haerder和Reuter在1983年中提出了事务的隔离性并提出术语 “ACID”,自此,事务的ACID四个性质成为业内标准术语 Pool未提交事务所修改的脏页刷回到持久存储,为了保证原子性, 先把Undo Log写入日志文件。Undo Log记录修改数据对象的旧值(Before Image, BFIM) Solution: Logging 15 缓冲区管理策略和事务恢复的关系 Force No-Force Steal Undo / No-Redo Undo + Redo (performance: fastest0 码力 | 42 页 | 2.12 MB | 1 年前3
共 187 条
- 1
- 2
- 3
- 4
- 5
- 6
- 19