Not sure who asks for these features. Writing some magic placeholders inside plain SQL is really confusing. You have no clue at the end where the value comes from. All SQL parameters and inputs should always just be directly mapped and not magically appear or be injected from some custom extensions. What used to be simple interface for writing queries has turned into mess by allowing such behaviours. When testing this code now you always would have to provide additional context every time.
That's typically how open source software works. Someone shares a need, someone fills that need with a new feature, sometimes its the same person. Luckily, you don't have to use that feature if you don't want to!
Thank you for the nice overview.
Happy New Year, Simon, from Josh and DaShaun!
Not sure who asks for these features. Writing some magic placeholders inside plain SQL is really confusing. You have no clue at the end where the value comes from. All SQL parameters and inputs should always just be directly mapped and not magically appear or be injected from some custom extensions. What used to be simple interface for writing queries has turned into mess by allowing such behaviours. When testing this code now you always would have to provide additional context every time.
That's typically how open source software works. Someone shares a need, someone fills that need with a new feature, sometimes its the same person. Luckily, you don't have to use that feature if you don't want to!