Jak pisać zapytania SQL za pomocą quizu AI

Odpowiedzi i wyjaśnienia pojawiają się w miarę rozwiązywania quizu.

1. Według przewodnika, który krok najbardziej poprawia dokładność kodu SQL generowanego przez sztuczną inteligencję?
   • Asking the model to be extra careful
   • Pasting your schema, such as CREATE TABLE statements and relationships
   • Writing your question entirely in uppercase
   • Always using the newest model available
2. Dlaczego powinieneś powiedzieć AI, jakiego dialektu SQL używasz?
   • Only PostgreSQL supports SELECT statements
   • AI models refuse to answer without a dialect
   • The dialect determines how much disk space a query uses
   • Dialects differ in details like date functions and LIMIT versus TOP
3. Łączysz zamówienia z Order_items, a następnie obliczasz SUM(orders.total). Jaki jest prawdopodobny problem?
   • Revenue is inflated because each order total repeats once per item
   • The query will always fail with a syntax error
   • NULL values are converted to zero
   • The results come back sorted in the wrong order
4. Dlaczego przewodnik zaleca poproszenie sztucznej inteligencji o wyjaśnienie zapytania prostymi słowami?
   • It makes the query run faster
   • SQL engines require an explanation before executing
   • It exposes misunderstandings, such as counting rows instead of distinct customers
   • It reduces the cost of the AI request
5. Które stwierdzenie dotyczące COUNT(kolumna) i COUNT(*) jest poprawne?
   • They always return the same number
   • COUNT(column) skips NULLs, while COUNT(*) counts every row
   • COUNT(*) skips NULLs, while COUNT(column) counts every row
   • COUNT(column) counts only distinct values
6. What is the safest way to experiment with AI-generated queries?
   • Run them directly on production during quiet hours
   • Ask the AI whether the query is safe and trust the answer
   • Use a read-only database user and wrap data changes in a transaction you can roll back
   • Remove the WHERE clause so the query is simpler
7. When asking an AI to optimize a slow query, what should you provide besides the query?
   • A screenshot of the dashboard that uses it
   • The database password
   • A list of everyone who runs the report
   • The execution plan from EXPLAIN or EXPLAIN ANALYZE
8. Which of these is a misconception the guide warns against?
   • A query that runs without errors must be returning the right answer
   • The schema alone is often enough context, without real customer data
   • An UPDATE without a WHERE clause affects every row
   • Business rules like amounts stored in cents should be stated