Cómo convertir SQL entre dialectos de bases de datos con AI Quiz

Las respuestas y explicaciones aparecen a medida que realiza el cuestionario.

1. ¿Qué información debe acompañar a una solicitud de IA para traducir una consulta entre dialectos SQL?
   • The source query alone, without either schema
   • Only the destination engine and the current row count
   • Both engines and versions, relevant schema and expected results
   • Only the source execution plan, without expected results
2. ¿Por qué una consulta que funciona en una tabla SQLite de tipo flexible no prueba que funcionará bajo el esquema de destino?
   • The destination may enforce different type and conversion rules
   • SQLite column affinity guarantees identical type enforcement in every engine
   • A query accepting a value locally proves it is valid for the target column
   • Column type declarations eliminate all engine-specific conversions
3. Un informe devuelve las diez primeras filas sin un orden definido. ¿Qué se debe aclarar antes de comparar los resultados ordenados entre motores?
   • Whether both queries specify the same limit, regardless of order
   • Whether the current storage layout happens to return matching rows
   • Whether the engines initially show the same first ten rows once
   • The intended deterministic ordering and top-set selection
4. En PostgreSQL, ¿qué distinción debe conservar un traductor entre comillas dobles y simples?
   • Both forms always denote ordinary string literals
   • Double quotes delimit identifiers; single quotes delimit ordinary string literals
   • Double quotes are only for numeric values
   • Single quotes preserve identifier case in every reference
5. Dos consultas traducidas muestran valores similares. ¿Qué comparación adicional puede exponer una diferencia significativa?
   • Only whether both results contain the same total number of rows
   • Only whether a few sampled displayed cells match
   • Row membership, duplicate counts and resulting data types
   • Only whether both statements execute without a syntax error
6. Why should parameter placeholder syntax be checked against the target driver as well as the database?
   • Binding conventions also depend on the client API
   • Every database driver uses the same placeholder format
   • Parameterization must always be removed during migration
   • Placeholder names determine the query's output sort order
7. The converted SQL parses successfully. Which claim still requires execution evidence?
   • That the destination recognizes its syntax
   • That the statement was accepted by the parser
   • That the query can be examined in a test environment
   • That it preserves the source query's intended results
8. After establishing that source and destination results agree, which concern should be measured separately?
   • Whether result equivalence can be assumed without fixtures
   • Performance and the destination's execution strategy
   • Whether testing can replace the intended business meaning
   • Whether all destination indexes must match source index names