Coding and Data
A query cannot be reviewed honestly without the schema and expected cardinality. Include both.
Review this SQL query using the supplied schema and expected result. Check join cardinality, null handling, duplicate rows, filtering order, transaction assumptions, injection risk and index use. Propose a corrected query only when needed, and explain how to verify it with EXPLAIN or the database equivalent. Database: [DATABASE AND VERSION]. Schema: [SCHEMA]. Query: [QUERY]. Expected result: [EXPECTED RESULT].DATABASE AND VERSIONSCHEMAQUERYEXPECTED RESULTCorrectness findings, a safer query where justified and a measurement plan rather than invented speed claims.
AI output can be incomplete or wrong. Verify facts, run code, check citations and keep private data out of tools that your organization has not approved.
Subscribe now to keep reading and get access to the full archive.