{}KDevTool
SQL & Database

SQL Parameter Binder

Paste a JDBC/Hibernate SQL query with ? placeholders together with its `binding parameter` log lines to get a ready-to-run query with real values inlined — strings quoted, numbers left raw and [null] turned into NULL. Supports both Hibernate 5 and Hibernate 6 log formats and runs entirely in your browser.

Paste SQL Query + Binding Parameters

Please paste an SQL query with binding parameters

How to use:

  1. Paste your SQL query (first line)
  2. Optionally paste binding parameter log lines to bind values into ? placeholders
  3. Values are formatted by JDBC type — strings quoted, numbers left raw, [null] becomes NULL
  4. Supports Hibernate 6 (1:VARCHAR) <- [v] and Hibernate 5 [1] as [VARCHAR] - [v] formats
  5. If no binding parameters are found, the SQL is shown as-is

About this tool

The SQL Parameter Binder solves a daily annoyance for Java and Spring Boot developers: a Hibernate-logged query prints the SQL with ? placeholders on one line and the actual parameter values on separate binding parameter log lines below it. This tool stitches them back together into a single, runnable query with the real values inlined.

Paste the SQL and the binding lines, and it fills each ? in order — quoting strings, leaving numbers raw and turning [null] into NULL — so you can copy the finished query straight into a database console to reproduce a bug. It understands both Hibernate 5 and Hibernate 6 log formats and runs entirely in your browser.

How to use

  1. Copy the SQL line with ? placeholders from your application log.
  2. Copy the accompanying binding parameter log lines that follow it.
  3. Paste both into the tool's input.
  4. The binder matches each value to its placeholder in order.
  5. Read the completed query with strings quoted and nulls as NULL.
  6. Copy it into your database console to run or debug the exact query.

Features

  • Fills ? placeholders from Hibernate binding parameter log lines.
  • Supports both Hibernate 5 and Hibernate 6 log formats.
  • Quotes string values and leaves numeric values raw.
  • Converts [null] bindings into proper SQL NULL.
  • Preserves placeholder order so values land in the right columns.
  • Turns a split log into a query you can run directly to reproduce bugs.
  • Fully client-side — your query and logged values never leave the browser.

Frequently asked questions

Are my SQL logs sent to a server?

No. The binder runs entirely in your browser, so your query and the logged parameter values — which may contain production data — never leave your device.

Which Hibernate log formats are supported?

It recognises both the Hibernate 5 and Hibernate 6 styles of binding parameter log output, so you can paste logs from either version without reformatting.

How are different value types handled?

String values are wrapped in single quotes, numbers are inlined without quotes so they stay numeric, and a [null] binding is replaced with the SQL keyword NULL.

Why do the values need to be in order?

JDBC binds parameters positionally, so the first ? gets the first logged value, the second ? the second, and so on. The tool relies on that order to place each value in the correct spot.

What is this most useful for?

Reproducing a production bug. Instead of guessing what values a query ran with, you paste the log and get the exact SQL to run in a console against a copy of the database.