4859. Spatial Data: bounding-box prefilter — Build success, failure, concurrency and scale tests. — School ERP — Go database/sql
DBMS
Published
Updated
0
Views
Verified
Scenario: A School ERP application must handle bounding-box prefilter. Build success, failure, concurrency and scale tests. Explain the invariant, SQL strategy, transaction/locking behavior, failure handling, observability and test plan. Use MySQL 8-oriented syntax where applicable.
Looking for the latest
Sarkari Result 2026
updates?
Check the latest government exam
results, merit lists and result updates
on Sarkari Resultess.
Answer & Explanation
4
Answers
Verified
Option 1: Run bounding-box prefilter without defining transaction boundaries, retry behavi
Run bounding-box prefilter without defining transaction boundaries, retry behavior, or production validation.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.
Verified
Correct Answer
Option 2: Use a parameterized, transaction-aware MySQL 8 implementation for bounding-box p
Use a parameterized, transaction-aware MySQL 8 implementation for bounding-box prefilter, validate the invariant, and explicitly test concurrency, retries and recovery.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.
Verified
Option 3: Use unparameterized dynamic SQL and rely only on application-side validation for
Use unparameterized dynamic SQL and rely only on application-side validation for bounding-box prefilter.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.
Verified
Option 4: Disable database protections and repair inconsistent rows manually after boundin
Disable database protections and repair inconsistent rows manually after bounding-box prefilter runs.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.