dbutil_messages.mes 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114
  1. # Copyright (C) 2012 Internet Systems Consortium, Inc. ("ISC")
  2. #
  3. # Permission to use, copy, modify, and/or distribute this software for any
  4. # purpose with or without fee is hereby granted, provided that the above
  5. # copyright notice and this permission notice appear in all copies.
  6. #
  7. # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  8. # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  9. # AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  10. # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  11. # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  12. # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  13. # PERFORMANCE OF THIS SOFTWARE.
  14. # No namespace declaration - these constants go in the global namespace
  15. # of the ddns messages python module.
  16. # When you add a message to this file, it is a good idea to run
  17. # <topsrcdir>/tools/reorder_message_file.py to make sure the
  18. # messages are in the correct order.
  19. % DBUTIL_BACKUP created backup of %1 in %2
  20. A backup for the given database file was created. Same of original file and
  21. backup are given in the output message.
  22. % DBUTIL_CHECK_ERROR unable to check database version: %1
  23. There was an error while trying to check the current version of the database
  24. schema. The error is shown in the message.
  25. % DBUTIL_CHECK_NOCONFIRM --noconfirm is not compatible with --check
  26. b10-dbutil was called with --check and --noconfirm. --noconfirm only has
  27. meaning with --upgrade, so this is considered an error.
  28. % DBUTIL_CHECK_OK this is the latest version of the database schema. No upgrade is required
  29. The database schema version has been checked, and is up to date.
  30. No action is required.
  31. % DBUTIL_CHECK_UPGRADE_NEEDED re-run this program with the --upgrade switch to upgrade
  32. The database schema version is not up to date, and an update is required.
  33. Please run the dbutil tool again, with the --upgrade argument.
  34. % DBUTIL_COMMAND_NONE must select one of --check or --upgrade
  35. b10-dbutil was called with neither --check nor --upgrade. One action must be
  36. provided.
  37. % DBUTIL_COMMAND_UPGRADE_CHECK --upgrade is not compatible with --check
  38. b10-dbutil was called with both the commands --upgrade and --check. Only one
  39. action can be performed at a time.
  40. % DBUTIL_DATABASE_MAY_BE_CORRUPT database file %1 may be corrupt, restore it from backup (%2)
  41. The upgrade failed while it was in progress; the database may now be in an
  42. inconsistent state, and it is advised to restore it from the backup that was
  43. created when b10-dbutil started.
  44. % DBUTIL_EXECUTE Executing SQL statement: %1
  45. Debug message; the given SQL statement is executed
  46. % DBUTIL_FILE Database file: %1
  47. The database file that is being checked.
  48. % DBUTIL_NO_FILE must supply name of the database file to upgrade
  49. b10-dbutil was called without a database file. Currently, it cannot find this
  50. file on its own, and it must be provided.
  51. % DBUTIL_STATEMENT_ERROR failed to execute %1: %2
  52. The given database statement failed to execute. The error is shown in the
  53. message.
  54. % DBUTIL_TOO_MANY_ARGUMENTS too many arguments to the command, maximum of one expected
  55. There were too many command-line arguments to b10-dbutil
  56. % DBUTIL_UPGRADE_CANCELED upgrade canceled; database has not been changed
  57. The user aborted the upgrade, and b10-dbutil will now exit.
  58. % DBUTIL_UPGRADE_DBUTIL please get the latest version of b10-dbutil and re-run
  59. A database schema was found that was newer than this version of dbutil, which
  60. is apparently out of date and should be upgraded itself.
  61. % DBUTIL_UPGRADE_FAILED upgrade failed: %1
  62. While the upgrade was in progress, an unexpected error occurred. The error
  63. is shown in the message.
  64. % DBUTIL_UPGRADE_NOT_ATTEMPTED database upgrade was not attempted
  65. Due to the earlier failure, the database schema upgrade was not attempted,
  66. and b10-dbutil will now exit.
  67. % DBUTIL_UPGRADE_NOT_NEEDED database already at latest version, no upgrade necessary
  68. b10-dbutil was told to upgrade the database schema, but it is already at the
  69. latest version.
  70. % DBUTIL_UPGRADE_NOT_POSSIBLE database at a later version than this utility can support
  71. b10-dbutil was told to upgrade the database schema, but it is at a higher
  72. version than this tool currently supports. Please update b10-dbutil and try
  73. again.
  74. % DBUTIL_UPGRADE_PREPARATION_FAILED upgrade preparation failed: %1
  75. An unexpected error occurred while b10-dbutil was preparing to upgrade the
  76. database schema. The error is shown in the message
  77. % DBUTIL_UPGRADE_SUCCESFUL database upgrade successfully completed
  78. The database schema update was completed successfully.
  79. % DBUTIL_UPGRADING upgrading database from %1 to %2
  80. An upgrade is in progress, the versions of the current upgrade action are shown.
  81. % DBUTIL_VERSION_CURRENT database version %1
  82. The current version of the database schema.
  83. % DBUTIL_VERSION_HIGH database is at a later version (%1) than this program can cope with (%2)
  84. The database schema is at a higher version than b10-dbutil knows about.
  85. % DBUTIL_VERSION_LOW database version %1, latest version is %2.
  86. The database schema is not up to date, the current version and the latest
  87. version are in the message.