view release on metacpan or  search on metacpan

lib/sqitchtutorial-oracle.pod  view on Meta::CPAN

  not ok

  Verify Summary Report
  ---------------------
  Changes: 1
  Errors:  1
  Verify failed

It's even nice enough to tell us what the problem is. Or, for the
divide-by-zero example, change the schema name:

  SELECT 1/COUNT(*) FROM sys.all_users WHERE username = 'NONESUCH';

Then the verify will look something like:

  > sqitch verify db:oracle://scott:tiger@/flipr_test
  Verifying db:oracle://scott:@/flipr_test
    * appschema ..   SELECT 1/COUNT(*) FROM sys.all_users WHERE username = 'NONESUCH'
            *
  ERROR at line 1:
  ORA-01476: divisor is equal to zero



  # Verify script "verify/appschema.sql" failed.
  not ok

  Verify Summary Report
  ---------------------
  Changes: 1
  Errors:  1
  Verify failed

Less useful error output, but enough to alert us that something has gone
wrong.

Don't forget to change the schema name back before continuing!

=head2 Status, Revert, Log, Repeat

For purely informational purposes, we can always see how a deployment was
recorded via the L<C<status>|sqitch-status> command, which reads the registry
tables from the database:

  > sqitch status db:oracle://scott:tiger@/flipr_test
  # On database db:oracle://scott:@/flipr_test
  # Project:  flipr
  # Change:   c59e700589fc03568e8f35f592c0d9b7c638cbdd
  # Name:     appschema
  # Deployed: 2013-12-31 15:25:23 -0800
  # By:       Marge N. O’Vera <marge@example.com>
  # 
  Nothing to deploy (up-to-date)

Let's make sure that we can revert the change:

  > sqitch revert db:oracle://scott:tiger@/flipr_test 
  Revert all changes from db:oracle://scott:@/flipr_test? [Yes] 
    - appschema .. ok

The L<C<revert>|sqitch-revert> command first prompts to make sure that we
really do want to revert. This is to prevent unnecessary accidents. You can
pass the C<-y> option to disable the prompt. Also, notice the C<-> before the
change name in the output, which reinforces that the change is being
I<removed> from the database. And now the schema should be gone:

  > echo "SELECT username FROM all_users WHERE username = 'FLIPR';" \
  | sqlplus -S scott/tiger@flipr_test
  no rows selected
  
And the status message should reflect as much:

  > sqitch status db:oracle://scott:tiger@/flipr_test
  # On database db:oracle://scott:@/flipr_test
  No changes deployed

Of course, since nothing is deployed, the L<C<verify>|sqitch-verify> command
has nothing to verify:

  > sqitch verify db:oracle://scott:tiger@/flipr_test
  Verifying db:oracle://scott:@/flipr_test
  No changes deployed

However, we still have a record that the change happened, visible via the
L<C<log>|sqitch-log> command:

  > sqitch log db:oracle://scott:tiger@/flipr_test
  On database db:oracle://scott:@/flipr_test
  Revert c59e700589fc03568e8f35f592c0d9b7c638cbdd
  Name:      appschema
  Committer: Marge N. O’Vera <marge@example.com>
  Date:      2013-12-31 16:19:38 -0800

      App user and schema for all flipr objects.

  Deploy c59e700589fc03568e8f35f592c0d9b7c638cbdd
  Name:      appschema
  Committer: Marge N. O’Vera <marge@example.com>
  Date:      2013-12-31 15:25:23 -0800

      App user and schema for all flipr objects.

Note that the actions we took are shown in reverse chronological order, with
the revert first and then the deploy.

Cool. Now let's commit it.

  > git add .
  > git commit -m 'Add flipr schema.'
  [main e0e0b11] Add flipr schema.
   4 files changed, 11 insertions(+)
   create mode 100644 deploy/appschema.sql
   create mode 100644 revert/appschema.sql
   create mode 100644 verify/appschema.sql

And then deploy again. This time, let's use the C<--verify> option, so that
the C<verify> script is applied when the change is deployed:

  > sqitch deploy --verify db:oracle://scott:tiger@/flipr_test
  Deploying changes to db:oracle://scott:@/flipr_test
    + appschema .. ok

And now the schema should be back: