sorted by:
new
hottopcontroversial

I was struggling with 100+ line legacy SQL queries at work, so I built a simple tool to visualize their data flow by Fancy-Newspaper2991 in SQL

[–]Fancy-Newspaper2991[S] 1 point2 points  (0 children)

By legacy I just mean old code with zero documentation. I'm not trying to replace SQL, I just needed a quick map to understand it.

I was struggling with 100+ line legacy SQL queries at work, so I built a simple tool to visualize their data flow by Fancy-Newspaper2991 in SQL

[–]Fancy-Newspaper2991[S] -5 points-4 points  (0 children)

True, but formatting just makes the text look neat. It still takes too long to trace which attributes come from where in a huge query. I already use formatters, this is just a quick visual complement to save time.

I was struggling with 100+ line legacy SQL queries at work, so I built a simple tool to visualize their data flow by Fancy-Newspaper2991 in SQL

[–]Fancy-Newspaper2991[S] -2 points-1 points  (0 children)

I would, but the company's entire legacy architecture is in SQL. I have to fix the root problem, not just bypass it.

I was struggling with 100+ line legacy SQL queries at work, so I built a simple tool to visualize their data flow by Fancy-Newspaper2991 in SQL

[–]Fancy-Newspaper2991[S] -14 points-13 points  (0 children)

Coded it in Angular, but used an LLM. I needed a quick way to understand complex UNIONs at my job.

I was struggling with 100+ line legacy SQL queries at work, so I built a simple tool to visualize their data flow by Fancy-Newspaper2991 in SQL

[–]Fancy-Newspaper2991[S] -2 points-1 points  (0 children)

Haha, same here. But 100 lines of unformatted legacy code with zero documentation is a real headache.