----- Original Message ----- From: "Tilghman Lesher" <[email protected]> > I think the smarter way, once you've gotten to this level of complexity, > is to > start using a real external database, such as Postgres, configure the ODBC > driver, and use func_odbc to interface to it. AstDB was never meant to be > such a general purpose database (indeed, queries to it are processed > serially, > not in parallel, as in real databases). > > --
Can you or anyone render an opinion on SQLite? Being so lightweight it's attractive as minimalist alternative to AstDB when all you want is to be able to retrieve multiple columns for a given primary key. Given its all-in-one-file design with no row-level locking (and no TABLE level locking--the entire database must be locked and released as a whole) it seems like it could be potentially problematic for a highly threaded application like Asterisk. Has anyone ever run into a real world limitation in Asterisk brought on by this SQLite global-locking design element? Any other idiosyncrasies with SQLite, that might make you recommend a jump straight to MySql or Postgres? _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
