There were some bugs in the very ancient version of Berkeley DB that Asterisk used. Instead of spending the time tracking down the bugs in the Berkeley code we move to the much better documented SQLite 3. Conversion of the old astdb happens at runtime by running the included astdb2sqlite3 utility. The ast_db API with SQLite 3 backend should behave identically to the old Berkeley backend, but in the future we could offer a much more robust interface. We do not include the SQLite 3 library in the source tree, but instead rely upon the distribution-provided libraries. SQLite is so ubiquitous that this should not place undue burden on administrators. git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@326589 65c4cc65-6c06-0410-ace0-fbb531ad65f3
12 lines
257 B
Text
12 lines
257 B
Text
GLIBC_2.0 {
|
|
global:
|
|
# the real DB entry point.
|
|
dbopen; __dbopen;
|
|
|
|
# The compatibility functions.
|
|
dbm_clearerr; dbm_close; dbm_delete; dbm_dirfno; dbm_error;
|
|
dbm_fetch; dbm_firstkey; dbm_nextkey; dbm_open; dbm_store;
|
|
local:
|
|
*;
|
|
};
|