summaryrefslogtreecommitdiff
path: root/UPGRADE.txt
diff options
context:
space:
mode:
authorTerry Wilson <twilson@digium.com>2011-10-10 22:54:03 +0000
committerTerry Wilson <twilson@digium.com>2011-10-10 22:54:03 +0000
commit6708ee76a0a0c42530fa89a528e0576c391f4390 (patch)
tree69cfc84bc6788f5ffff2568c5cb32e8da26a765e /UPGRADE.txt
parent4ec8d574542597c54c43a067540ba99a0710d977 (diff)
Merged revisions 340219-340220 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/10 ........ r340219 | twilson | 2011-10-10 15:38:06 -0700 (Mon, 10 Oct 2011) | 8 lines Add astdb conversion utility for Berkeley to SQLite 3 If someone wants to backtrack from Asterisk 1.8 to 10 they can use the astdb2bdb utility to convert the database back to the Berkeley format that Asterisk 1.8 uses. Review: https://reviewboard.asterisk.org/r/1502/ ........ r340220 | twilson | 2011-10-10 15:39:41 -0700 (Mon, 10 Oct 2011) | 2 lines Add a missing file for the astdb2bdb conversion utility ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@340221 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'UPGRADE.txt')
-rw-r--r--UPGRADE.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/UPGRADE.txt b/UPGRADE.txt
index c0ee9ca91..05df0a1c4 100644
--- a/UPGRADE.txt
+++ b/UPGRADE.txt
@@ -87,7 +87,9 @@ Asterisk Database:
SQLite 3. An existing Berkeley astdb file can be converted with the astdb2sqlite3
utility in the UTILS section of menuselect. If an existing astdb is found and no
astdb.sqlite3 exists, astdb2sqlite3 will be compiled automatically. Asterisk will
- convert an existing astdb to the SQLite3 version automatically at runtime.
+ convert an existing astdb to the SQLite3 version automatically at runtime. If
+ moving back from Asterisk 10 to Asterisk 1.8, the astdb2bdb utility can be used
+ to create a Berkeley DB copy of the SQLite3 astdb that Asterisk 10 uses.
Manager:
- The AMI protocol version was incremented to 1.2 as a result of changing two