A space to connect knowledge, one line of code a day.
Discover tutorials, ideas, and notes from a learning journey.
Build a focused web pentest plan with clear authorization, realistic objectives, controlled testing, and evidence that developers can use.
To configure c3p0 as a JDBC connection pool, you typically: create a DataSource (usually ComboPooledDataSource) tune pool parameters (min/max pool size, idle time, timeouts, statement cache) use the DataSource everywhere instead of DriverManager.getConnection(…) close Connection/Statement/ResultSet normally (c3p0 returns connections to the pool on close()) Below are the common ways to do it. 1) Programmatic configuration […]
To configure an Apache DBCP connection pool for “plain” JDBC, you typically create a pooled DataSource once at startup, then get connections from it (and always close them to return to the pool). Below are the two most common approaches. 1) Recommended (DBCP2): BasicDataSource (simplest) Create and configure the pool package org.kodejava.jdbc; import org.apache.commons.dbcp2.BasicDataSource; import […]
To use connection pooling in plain JDBC with HikariCP, the main shift is: stop using DriverManager.getConnection(…) everywhere create one DataSource (the pool) at startup whenever you need a DB connection, call dataSource.getConnection() always close resources with try-with-resources (closing returns the connection to the pool, it does not kill the physical connection) 1) Create a pooled […]
Savepoints in JDBC provide fine-grained control over transactions by allowing you to roll back to a specific point within a transaction rather than undoing everything. This is particularly useful for handling optional operations or partial failures. Key Steps to Use Savepoints Disable Auto-commit: Savepoints only work within a manual transaction. Set a Savepoint: Use connection.setSavepoint() […]
Using transactions in JDBC is essential when you need to ensure that a group of SQL statements either all succeed or all fail together (maintaining Atomicity). By default, a JDBC Connection is in auto-commit mode, meaning every single SQL statement is treated as its own transaction and committed immediately. To manage transactions manually, follow these […]
To set the fetch size for large queries in Java using JDBC, you use the setFetchSize(int rows) method on a Statement or PreparedStatement object. This gives the JDBC driver a hint as to the number of rows that should be fetched from the database when more rows are needed. This is particularly useful for large […]
Stay curious. There is always something new to learn.
Writer and founder of Diary Coding — sharing notes, tutorials, and experiences about programming for anyone who wants to keep learning.