SQLcl is a great tool, but it has its problems when it comes to environments other than English/US.
I show a couple of Problems and Strangenesses here and give examples how to work around them.
Ever tried to sort Version-Strings with pure SQL – for example when you want to find the highest Flyway version installed in your database?
Let me show you how you can!
My previous solution to split a string into rows by a delimiter, using pure SQL had a couple of small flaws.
Here is the revisited version that also removes a bit of code duplication.
Steven Feuerstein will do some live refactoring in his “Feuertips” episode #13.
However, in order to confidently refactor, one could use some automated tests that ensure the functionality doesn’t change…
Sometimes we have data that is not split into columns and rows, but SQL can only really thrive on structured data.
But thanks to recursive queries we can split any string into rows – with pure SQL.
It is a common practice to eliminate possible NULL values from your method’s parameters, and in the past I advocated to use subtypes to do this in PL/SQL.
However, it doesn’t work from SQL…
Thanks to my trainees I learned a new term: “List Comprehension”. But what is it and does it only exist in Python?
I just completed #AdventOfCode in #SQL – Day 11 – “Seating System”
Game of Life implementation with the help of the MODEL clause and also in PL/SQL, showing the limits of SQL
I just completed #AdventOfCode in #SQL – Day 10 – “Adapter Array”
WHAT THE SITH DID I JUST DO IN PLAIN SQL?
I just completed #AdventOfCode in #SQL – Day 9 – “Encoding Error”
Who said you HAD to use a set-based approach when writing SQL?
Part 2 shows that we *can* implement complex recursive algorithms if we want.