github-forks
/
HikariCP
mirror of https://github.com/brettwooldridge/HikariCP.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update README.md

Browse Source
pull/192/head
Brett Wooldridge 10 years ago
parent 4cec3af51f
commit 88a73ec853
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File

8
README.md
Unescape Escape View File

@ -239,12 +239,12 @@ property only applies if ``autoCommit`` is disabled. *Default: false*
***Missing Knobs***<br/> ***Missing Knobs***<br/>
HikariCP has plenty of "knobs" to turn as you can see above, but comparatively less than some other pools. HikariCP has plenty of "knobs" to turn as you can see above, but comparatively less than some other pools.
This is a design philosophy. The HikariCP design asthetic is Minimalism. In keeping with the This is a design philosophy. The HikariCP design asthetic is Minimalism. In keeping with the
*simple is better* or *less is more* design philosophy, some knobs and features are intentionally left out. *simple is better* or *less is more* design philosophy, some knobs are intentionally left out. Here are two,
Here are two, and the rationale. and the rationale.
**Statement Cache**<br/> **Statement Cache**<br/>
Most major database JDBC drivers already have a Statement cache that can be configured (Oracle, Most major database JDBC drivers already have a Statement cache that can be configured
[MySQL](https://github.com/brettwooldridge/HikariCP/wiki/MySQL-Configuration), PostgreSQL, Derby, etc). ([MySQL](https://github.com/brettwooldridge/HikariCP/wiki/MySQL-Configuration), PostgreSQL, Derby, etc).
A statement cache in the pool would add unneeded weight and no additional functionality. It is simply A statement cache in the pool would add unneeded weight and no additional functionality. It is simply
unnecessary with modern database drivers to implement a cache at the pool level. unnecessary with modern database drivers to implement a cache at the pool level.

Write Preview
Loading…
Cancel
Save