commit | 5b25f8b1d6637d24a3145b569dad829e915b58d2 | [log] [tgz] |
---|---|---|
author | Nico Sallembien <nsallembien@google.com> | Tue Mar 16 11:06:31 2010 -0700 |
committer | Nico Sallembien <nsallembien@google.com> | Wed Mar 17 08:59:46 2010 -0700 |
tree | 97ce5aedd65a81495909565cf8cb8951771b6bf2 | |
parent | 8d9fc99a6a5a5334b98fab9de7fdd0fd26f060bc [diff] |
Allow schema upgrades to display messages It's possible that the execution of a SQL statement is not critical to the success of a schema upgrade. An example of this is a function that during the upgrade gets removed from the database. It is possible that this function may have been removed by the user manually, and the fact that it is already missing should not block the upgrade from proceeding. Bug: 500 Change-Id: Ie9aa0d732f884a6d749d864ee3a43d257af272b7