> Chris, While you are thinking logically, This will just as > un-effective as putting them all in the dialplan, as the DBGet() and > DBPut() functionality deals with the internal astdb (db1 database).
DBGet and DBPut work with Berkely DB 1.85. Althought this DB185 is a little outdated, it can easily handle one million datasets and return fast results. You can put stuff into it with any DB185 enabled program, e.g. there are modules for DB185 in Perl and in Python (if python compiled with the right compiler switches). However, a DB185 file is very much like a flat file with an index/hash for fast lookup, so there is nothing like different tables like in SQL. That means that you get all your data into one, big file, e.g. Asterisks internal registration data and your lookup stuff. If you still dislike astdb, another idea: then there was talk about a Patch about SQL commands in the dialplan in asterisk-dev. _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
