Kuiz berkaitan panduan · Sederhana Tahap

Cara Menyahpepijat Ralat SQL dengan Kuiz AI

Amalkan diagnosis ralat SQL, pengelompokan pembaikan dan pengesahan keputusan menggunakan lajur samar-samar, skema yang diubah dan lekapan ujian kecil.

Laluan panduan yang berkaitanNyahpepijat Ralat Sql Dengan AI
soalan 1 daripada 8

Dua jadual bercantum kedua-duanya mengandungi id, dan output yang dimaksudkan ialah pengecam pelanggan. Pembaikan yang manakah menangani kekaburan itu?

Pratonton setiap soalan8 soalan

Jawapan dan penjelasan muncul semasa anda mengambil kuiz.

  1. Dua jadual bercantum kedua-duanya mengandungi id, dan output yang dimaksudkan ialah pengecam pelanggan. Pembaikan yang manakah menangani kekaburan itu?
    • Qualify id with the customer table's alias
    • Choose either id because matching names imply identical values
    • Add every column to GROUP BY
    • Rename the output heading without qualifying the reference
  2. Mengapakah menambah setiap lajur yang dipilih pada GROUP BY boleh menjadi pembaikan yang lemah untuk laporan jumlah pelanggan?
    • It guarantees that all selected dates belong to the same customer summary
    • It preserves customer-level totals regardless of the added columns
    • It may change the result from one row per customer to a finer grouping
    • It automatically chooses the latest order date within each customer
  3. Ralat menunjukkan berhampiran penghujung ungkapan. Mengapakah token terdahulu juga perlu diperiksa?
    • The marked token must always be the first incorrect token
    • Only the final clause can affect parsing near the end
    • Name-resolution errors can always be fixed by moving the marked token
    • An earlier missing comma or unmatched parenthesis can make a later token unexpected
  4. Maklumat manakah yang paling berguna apabila meminta AI menghasilkan semula kegagalan SQL?
    • The query and a paraphrase of the error, without identifying the engine
    • The engine, exact error, query, minimal schema and representative test rows
    • Only a successful version from another database engine
    • Only the expected output, without the query or schema
  5. Pernyataan SQL yang dibaiki berjaya dilaksanakan. Cek mana yang masih penting?
    • Whether its rows, totals and null behavior match the intended result
    • Whether it returns the same row count, without checking values
    • Whether it has the same output headings, without checking totals
    • Whether it runs once without an error on an empty fixture
  6. A cast succeeds for most rows but fails for one unexpected text value. Which debugging step targets that failure?
    • Remove the type information from the prompt
    • Assume the query is syntactically invalid in every context
    • Include the failing value in a reduced test fixture
    • Add an unrelated join to change the execution plan
  7. Why is PostgreSQL EXPLAIN ANALYZE inappropriate as a harmless syntax check for an untrusted modifying query?
    • It never reports actual execution behavior
    • It only checks table aliases
    • It always skips the statement's write operations
    • It actually executes the statement
  8. An application query uses bound parameters. Why should a reproduction preserve their types?
    • Parameter types cannot affect a database operation
    • Substituted literals can behave differently from the original bound values
    • Every parameter should be converted to text before testing
    • A bound parameter always removes the need to check casts