Knowledge is power and knowing more deeply about what your database is capable of is very helpful. It's worth knowing every tool in your tool chest! That said,

Knowledge is power and knowing more deeply about what your database is capable of is very helpful. It's worth knowing every tool in your tool chest! That said, be careful with going too overboard with one specific tool (SQL). You may find yourself using a hammer for everything, when another tool may be more appropriate. More specifically, it's easy to abuse advanced SQL constructs to create a mess for yourself. Too much business logic in the database is something I've seen become a nightmare for other programmers looking at software later. :) This post[0] goes a bit into more detail about explaining where you should keep your "business logic" when choosing to put it in code or into SQL. 0: https://softwareengineering.stackexchange.com/questions/194446/how-much-business-logic-should-the-database-implement https://softwareengineering.stackexchange.com/questions/1944...