String Functions

String Functions is a practical SQL concept used to design, query, secure, operate, or analyze relational data correctly.

Lesson content

String Functions String Functions is a practical SQL concept used to design, query, secure, operate, or analyze relational data correctly. Example SELECT UPPER(name), ROUND(price, 2), CURRENT_DATE FROM products; Key point Use the smallest correct statement, test it with representative data, and verify constraints and performance before production use. Real-life example A sales manager needs a monthly report showing revenue, order counts, rankings, and changes over time without exporting raw data to a spreadsheet. Advanced example BEGIN; -- Preview the exact target set first. SELECT id FROM orders WHERE status = 'pending'; -- Apply the String Functions operation, verify affected rows, then commit. COMMIT; Expected result The query returns only the intended rows and columns, with deterministic ordering where order matters. Production check Test with empty, duplicate, null, and boundary values. Use a transaction for related writes. Inspect the execution plan before adding an index. Use parameterized queries for application input. Continue with the PicoStore database This lesson reuses picostore . Relevant tables: customers, products, orders, order_items . Keep the starter rows from the Introduction lesson so results remain comparable. Another practical example SELECT category, COUNT(*) AS products, ROUND(AVG(price), 2) AS average_price, SUM(stock) AS units_available FROM products GROUP BY category HAVING SUM(stock) > 0; Check the result Run the verification query, compare the returned rows with the starter data, and explain why every included or excluded row is correct. SQL reference catalog: String Functions This catalog covers the practical public SQL surface. Check the exact server-version documentation before using a vendor-specific item. Portable/common string functions UPPER — uppercase text LOWER — lowercase text CHAR_LENGTH / CHARACTER_LENGTH — number of characters OCTET_LENGTH — number of bytes TRIM — remove leading/trailing characters LTRIM — remove leading whitespace RTRIM — remove trailing whitespace SUBSTRING / SUBSTR — extract part of text POSITION — find substring position REPLACE — replace matching text CONCAT — join values NULLIF — return NULL when values match COALESCE — first non-null value MySQL string functions LENGTH — byte length LOCATE / INSTR — find substring LEFT / RIGHT — take characters from an end LPAD / RPAD — pad text REPEAT — repeat text REVERSE — reverse text SPACE — produce spaces STRCMP — compare strings FIND_IN_SET — find value in comma-separated text FIELD — position in a value list FORMAT — locale-aware number formatting GROUP_CONCAT — aggregate strings REGEXP_REPLACE / REGEXP_SUBSTR — regular-expression operations PostgreSQL string functions LENGTH — character length STRPOS — find substring LEFT / RIGHT — take characters from an end LPAD / RPAD — pad text REPEAT — repeat text REVERSE — reverse text SPLIT_PART — select a delimited part STRING_TO_ARRAY — split into an array ARRAY_TO_STRING — join an array STRING_AGG — aggregate strings FORMAT — formatted text INITCAP — capitalize words REGEXP_REPLACE / REGEXP_MATCH — regular-expression operations TRANSLATE — character-by-character replacement ASCII / CHR — character code conversion Easy example Start with a small customer table and retrieve active customers in a predictable order. SELECT customer_id, name, email FROM customers WHERE status = 'active' ORDER BY name; How to verify the easy example Run it with representative input. Confirm the expected output. Try one missing, invalid, or boundary value. Advanced example Use a CTE and a window function to rank customer revenue while keeping the query readable and testable. WITH customer_revenue AS ( SELECT customer_id, SUM(total_amount) AS revenue FROM orders WHERE order_status = 'completed' GROUP BY customer_id ) SELECT customer_id, revenue, DENSE_RANK() OVER (ORDER BY revenue DESC) AS revenue_rank FROM customer_revenue ORDER BY revenue_rank, customer_id; Advanced review Explain the tradeoffs and assumptions. Test failure, scale, security, and recovery behavior. Capture evidence from tests, execution plans, logs, or review output. Additional practical guidance String Functions: MySQL and PostgreSQL Prefer standard SQL functions when portability matters. MySQL and PostgreSQL differ most in date formatting, type conversion, string aggregation, and error handling for invalid values. Required verification Run the simple case. Test a NULL, duplicate, empty, or boundary case where relevant. Confirm the affected rows or query result. Use EXPLAIN for performance-sensitive queries.