SQL IN Clause Builder

In the default Auto mode the whole list is inspected: if every value is a plain decimal number the list stays unquoted, otherwise every value is single-quoted as a string. One non-numeric value flips the entire list to quoted.

Auto decides for you, Force numeric always leaves values bare, and Always quote always wraps them in quotes. The Force quote checkbox overrides the menu entirely and quotes everything, which is why it disables the Numbers dropdown.

They are escaped the SQL-standard way by doubling them, so O'Brien becomes 'O''Brien'. That keeps the clause valid when you paste it into most databases without breaking out of the string literal.

Yes. Turn on Dedupe to drop repeated values while keeping the first occurrence, and Sort to order them. Number lists sort numerically, so 2 comes before 10, while text lists sort alphabetically.

Use newlines, commas, or a mix of both. The builder splits on runs of newlines and commas together, trims whitespace around each value, and drops any empty entries, so messy pasted lists still come out clean.

Yes. Enter a column such as user_id in the Column field and the output becomes user_id IN (...). Leave it blank to get just the IN (...) fragment on its own.

It escapes apostrophes for known, trusted lists such as IDs you already have, but it is not a substitute for parameterized queries. For values that come from untrusted user input, bind them as parameters instead of pasting them into a clause.

The standard single-quote doubling works in PostgreSQL, SQLite, SQL Server and MySQL in default mode. If your MySQL session enables backslash escaping you may want to review string literals before running the query.

No. The clause is built entirely in your browser and nothing is sent to a server, so it is safe to use with sensitive IDs, emails and internal identifiers.