Kuiz berkaitan panduan · Sederhana Tahap

Cara Menulis SQL CTE dan Subquery dengan Kuiz AI

Semak skop CTE, EXISTS dan subkueri skalar serta perlindungan pertanyaan rekursif melalui laporan pelanggan dan contoh hierarki kecil.

Laluan panduan yang berkaitanSql Ctes Dan Subqueries Dengan AI
soalan 1 daripada 8

CTE PILIH bernama customer_totals ditakrifkan dengan WITH. Berapa lamakah hasil yang dinamakan biasa itu wujud?

Pratonton setiap soalan8 soalan

Jawapan dan penjelasan muncul semasa anda mengambil kuiz.

  1. CTE PILIH bernama customer_totals ditakrifkan dengan WITH. Berapa lamakah hasil yang dinamakan biasa itu wujud?
    • Until the database server next restarts
    • Within the larger statement that defines it
    • Until a separate DROP TABLE command removes it
    • Across every future query in the same application
  2. Seorang pelanggan mempunyai tiga pesanan yang layak. Bagaimanakah keadaan EXISTS mempengaruhi baris luar pelanggan tersebut?
    • It automatically creates three output copies
    • It adds three to every customer total
    • It fails because more than one inner row exists
    • It tests true without multiplying the row because of those matches
  3. Subquery skalar PostgreSQL secara tidak dijangka mengembalikan dua baris. Respons yang manakah mengekalkan peraturan pemilihan yang bermakna?
    • Clarify and implement which single value the query should return
    • Add an unordered LIMIT merely to suppress the error
    • Assume PostgreSQL will always choose the latest row
    • Change the output alias and leave the subquery unchanged
  4. Mengapakah pelanggan_jumlah CTE harus diuji sebelum menyertainya dengan butiran pelanggan?
    • The CTE name establishes that each customer key is unique
    • An aggregate inside a CTE cannot produce repeated customer keys
    • Unexpected repeated customer keys can multiply the later result
    • Checking only the final row count establishes each intermediate result's grain
  5. AI mendakwa bahawa menggantikan setiap subkueri dengan CTE sentiasa meningkatkan prestasi. Bagaimanakah ini harus dinilai?
    • Accept it because named steps always execute once
    • Check the target engine's behavior and execution plan
    • Accept it because a shorter query always requires less work
    • Reject every CTE because it must always be materialized
  6. Why might UNION fail to stop a recursive cycle when a depth column changes at each visit?
    • UNION preserves every exact duplicate by definition
    • Depth columns prevent any recursive query from running
    • Cycles can occur only in queries using UNION ALL
    • Repeated visits can remain distinct result rows because their depths differ
  7. A correlated subquery refers to an outer value. Which performance claim would be premature without plan evidence?
    • It must physically rerun a full independent query for every outer row
    • Its result logically depends on an outer value
    • An optimizer may transform an eligible expression
    • Its behavior should be tested on representative data
  8. Why should null-containing fixtures be used when rewriting a NOT IN condition?
    • Nulls always behave like ordinary equal values
    • NOT IN ignores every null in its comparison set
    • Nulls can change the condition's truth result and the rewrite's behavior
    • Adding a CTE automatically removes null-related differences