BCE dates cause subtle "off-by-one" bugs between Java and databases. dbVisitor 6.7.0 adds JulianDayTypeHandler and PgDateTypeHandler to solve this from two angles: cross-database portability and PostgreSQL-native support.

"Select two columns and build a Map" is a common pattern — ID-to-name, code-to-description, etc. The new queryForPairs in dbVisitor 6.7.0 returns a Map<K, V> directly in one call, no manual iteration needed.

PostgreSQL's pgvector extension enables vector storage and similarity search, but Java lacked a clean mapping. dbVisitor 6.7.0's PgVectorTypeHandler maps vector columns directly to List<Float> with full Fluent API support for CRUD and KNN queries.

Hundreds of lines of <if>, <where>, <choose> tags in MyBatis XML — clean SQL buried under mummy wrappings. If you're fed up with three lines of XML for a simple null check, dbVisitor's dynamic SQL rules might be the scissors you need.

As dbVisitor expanded from RDBMS to NoSQL, the dialect system's abstractions became fragmented. This post explains a deep architectural refactoring that unifies dialect metadata and command building into a cohesive design — no functional changes, pure structural improvement.

dbVisitor's "Two-Layer Adapter" unifies RDBMS and NoSQL access through two abstractions: Layer 1 — a unified API (LambdaTemplate / Mapper) hiding syntax differences; Layer 2 — JDBC-compliant drivers wrapping NoSQL protocols. Use the full stack, or plug just the driver into existing MyBatis/Hibernate projects.

After Next-Gen Data Access: dbVisitor went live, the core debate was direct: can a single API truly unify RDBMS and NoSQL? This post tackles the controversy and explains the design principles behind dbVisitor's "One APIs Access Any DataBase" vision.

Classic frameworks like Hibernate and MyBatis were built for an RDBMS-only world. As data diversifies into NoSQL, NewSQL, and vector stores, the real challenge shifts to unified access across all of them.

In hybrid projects with both MySQL and ElasticSearch, the data access layer often splits between MyBatis XML and complex DSL builders. dbVisitor lets you operate ElasticSearch using the same Mapper interfaces and XML, unifying your data access code.

In hybrid projects with both MySQL and MongoDB, the data access layer often feels fragmented — MyBatis Mapper on one side, MongoTemplate on the other. dbVisitor lets you operate MongoDB using the same Mapper interfaces and XML, achieving a unified architecture.