Sigh, what is it with these cowboy SQL Devs? Why the fuck is this a pattern for anything?

New contract, new idiots, sigh.

EDIT: Had to change picture because Prod is different to Dev (but no dev has been done since release....smh)

I see it's mssql, but I don't see what's wrong with this procedure for I have little to no knowledge of procedures.

Please explain thx

@perotti basically says

- Check if view exists
- Then check if the view exists
- and if it exists, drop the view if it exists and create otherwise just create.

Which could have all been dealt with the DROP VIEW IF EXISTS line and then CREATE. All the extra logic is redundant

What the fucking fuck? Wouldn't you just save the views? That makes no damn sense.

@segfault0xff i dont even know why these views exist in the first place. Its all nested nested nested views, stupid to maintain and debug, and this whole pattern in the screenshot is to solve a problem that no one decided to really think about solving in a scalable way.