Migrate "pretend" - view actual SQL queries before you run them
Laravel has convenient database migrations mechanism, which allows us to track database changes and easily roll them back if needed. But what is hiding behind the scenes? What if we need to know actual SQL queries that have been generated during the migration? Or another scenario - what if we want to check the SQLs before they are actually run? There's a trick for both of it.