sqlite3_datasrc_messages.mes 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142
  1. # Copyright (C) 2013 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. $NAMESPACE isc::datasrc
  15. # \brief Messages for the SQLITE3 data source backend
  16. % DATASRC_SQLITE_CLOSE closing SQLite database
  17. Debug information. The SQLite data source is closing the database file.
  18. % DATASRC_SQLITE_COMPATIBLE_VERSION database schema V%1.%2 not up to date (expecting V%3.%4) but is compatible
  19. The version of the SQLite3 database schema used to hold the zone data
  20. is not the latest one - the current version of BIND 10 was written
  21. with a later schema version in mind. However, the database is
  22. compatible with the current version of BIND 10, and BIND 10 will run
  23. without any problems.
  24. Consult the release notes for your version of BIND 10. Depending on
  25. the changes made to the database schema, it is possible that improved
  26. performance could result if the database were upgraded.
  27. % DATASRC_SQLITE_CONNCLOSE Closing sqlite database
  28. The database file is no longer needed and is being closed.
  29. % DATASRC_SQLITE_CONNOPEN Opening sqlite database file '%1'
  30. The database file is being opened so it can start providing data.
  31. % DATASRC_SQLITE_CREATE SQLite data source created
  32. Debug information. An instance of SQLite data source is being created.
  33. % DATASRC_SQLITE_DESTROY SQLite data source destroyed
  34. Debug information. An instance of SQLite data source is being destroyed.
  35. % DATASRC_SQLITE_DROPCONN SQLite3Database is being deinitialized
  36. The object around a database connection is being destroyed.
  37. % DATASRC_SQLITE_ENCLOSURE looking for zone containing '%1'
  38. Debug information. The SQLite data source is trying to identify which zone
  39. should hold this domain.
  40. % DATASRC_SQLITE_ENCLOSURE_NOT_FOUND no zone contains '%1'
  41. Debug information. The last SQLITE_ENCLOSURE query was unsuccessful; there's
  42. no such zone in our data.
  43. % DATASRC_SQLITE_FIND looking for RRset '%1/%2'
  44. Debug information. The SQLite data source is looking up a resource record
  45. set.
  46. % DATASRC_SQLITE_FINDADDRS looking for A/AAAA addresses for '%1'
  47. Debug information. The data source is looking up the addresses for given
  48. domain name.
  49. % DATASRC_SQLITE_FINDADDRS_BAD_CLASS class mismatch looking for addresses ('%1' and '%2')
  50. The SQLite data source was looking up A/AAAA addresses, but the data source
  51. contains different class than the query was for.
  52. % DATASRC_SQLITE_FINDEXACT looking for exact RRset '%1/%2'
  53. Debug information. The SQLite data source is looking up an exact resource
  54. record.
  55. % DATASRC_SQLITE_FINDEXACT_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')
  56. The SQLite data source was looking up an exact RRset, but the data source
  57. contains different class than the query was for.
  58. % DATASRC_SQLITE_FINDREC looking for record '%1/%2'
  59. Debug information. The SQLite data source is looking up records of given name
  60. and type in the database.
  61. % DATASRC_SQLITE_FINDREF looking for referral at '%1'
  62. Debug information. The SQLite data source is identifying if this domain is
  63. a referral and where it goes.
  64. % DATASRC_SQLITE_FINDREF_BAD_CLASS class mismatch looking for referral ('%1' and '%2')
  65. The SQLite data source was trying to identify if there's a referral. But
  66. it contains different class than the query was for.
  67. % DATASRC_SQLITE_FIND_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')
  68. The SQLite data source was looking up an RRset, but the data source contains
  69. different class than the query was for.
  70. % DATASRC_SQLITE_FIND_NSEC3 looking for NSEC3 in zone '%1' for hash '%2'
  71. Debug information. We're trying to look up a NSEC3 record in the SQLite data
  72. source.
  73. % DATASRC_SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1'
  74. The SQLite data source was asked to provide a NSEC3 record for given zone.
  75. But it doesn't contain that zone.
  76. % DATASRC_SQLITE_INCOMPATIBLE_VERSION database schema V%1.%2 incompatible with version (V%3.%4) expected
  77. The version of the SQLite3 database schema used to hold the zone data
  78. is incompatible with the version expected by BIND 10. As a result,
  79. BIND 10 is unable to run using the database file as the data source.
  80. The database should be updated using the means described in the BIND
  81. 10 documentation.
  82. % DATASRC_SQLITE_NEWCONN SQLite3Database is being initialized
  83. A wrapper object to hold database connection is being initialized.
  84. % DATASRC_SQLITE_OPEN opening SQLite database '%1'
  85. Debug information. The SQLite data source is loading an SQLite database in
  86. the provided file.
  87. % DATASRC_SQLITE_PREVIOUS looking for name previous to '%1'
  88. This is a debug message. The name given was not found, so the program
  89. is searching for the next name higher up the hierarchy (e.g. if
  90. www.example.com were queried for and not found, the software searches
  91. for the "previous" name, example.com).
  92. % DATASRC_SQLITE_PREVIOUS_NO_ZONE no zone containing '%1'
  93. The name given was not found, so the program is searching for the next
  94. name higher up the hierarchy (e.g. if www.example.com were queried
  95. for and not found, the software searches for the "previous" name,
  96. example.com). However, this name is not contained in any zone in the
  97. data source. This is an error since it indicates a problem in the earlier
  98. processing of the query.
  99. % DATASRC_SQLITE_SETUP setting up new SQLite3 database in '%1'
  100. The database for SQLite data source was found empty. It is assumed this is the
  101. first run and it is being initialized with current schema. It'll still contain
  102. no data, but it will be ready for use. If this is indeed the first run of
  103. BIND 10, it is to be expected and completely harmless. If you just configured
  104. a data source to point to an existing file and you see this, you may have
  105. misspelled the file name.
  106. % DATASRC_SQLITE_SETUP_OLD_API setting up new SQLite database
  107. The database for SQLite data source was found empty. It is assumed this is the
  108. first run and it is being initialized with current schema. It'll still contain
  109. no data, but it will be ready for use. This is similar to DATASRC_SQLITE_SETUP
  110. message, but it is logged from the old API. You should never see it, since the
  111. API is deprecated.