Water utility engineers open a pull request where one branch renames a meter column and another updates a dependent view that still references the old name. What is the correct conflict-resolution approach?
Select an answer to reveal the explanation.
Short Explanation
Renaming a meter column while a view still points at the old name is like swapping street numbers without updating the map—fix both objects in the same merge so the project still builds.
Full Explanation
Water utility engineers face a pull request conflict where one branch renames a meter column and another updates a dependent view that still references the old name. The correct conflict-resolution approach is to resolve the merge so the view DDL matches the renamed column and both objects build together in the SQL Database Project. Dependent municipal objects must remain a consistent model: meters, consumption views, and reporting contracts break if the table rename and view definition disagree. Coordinated resolution in the same merge is how SDK-style projects stay compilable and how CI build validation can pass for utility schema.
Keeping the old column name in the view forever while ignoring the table rename fails by leaving an unresolved reference—the project will not build as a coherent model. Dropping the view from the project without replacing its reporting contract fails consumers that depend on the view’s shape for meter analytics. Merging only the table rename and leaving the broken view for production to discover fails detection left-shift: production becomes the first compiler, which CI was meant to prevent.
Exam caveat: DDL merge conflicts involving dependencies are resolved by making the full object graph consistent in the project, not by partial merges or deleting dependents without a replacement contract. When stems mention renamed columns and views, look for answers that keep build integrity.
Operational check: after resolving the conflict, run the SDK-style project build locally and in PR CI; confirm the meter table rename and updated view both appear in the model and that packages publish without unresolved references. Execute a smoke query against the view in a test deploy targeting water meter data to verify column names align with the new physical table definition.