[Gamester17]

Would XBMC benifit from using ADOdb (or better yet ADOdb Lite) as an database abstraction layer between XBMC's SQL (video and music) databases and XBMC's Web Interface (HTTP API) and Python Scripts?
http://en.wikipedia.org/wiki/ADOdb
http://en.wikipedia.org/wiki/ADOdb_Lite

From what I understand having a ADOdb API to XBMC's SQL databases would also make it much easier to make calls to XBMC's SQL databases from the Web Interface (HTTP API) and Python Scripts, (which HTTP API client developers and python coders would use), and it could also be used as a direct and 'live' networked interface from third-party media managers such as "Media Info Plus", "Media Companion", "MeD's Movie Manager", "Invelos's DVD Profiler", "My Movies", and similar desktop media management software for computers.

Feature request ticked on trac: http://trac.xbmc.org/ticket/4946

Good idea or not for XBMC?

[Soju]

Heres an interesting discussion. Whats not mentioned is the variability and scalability encountered when you sink an embedded db and a server. Locking contentions and replication, among many other factors are important. If you want to dictate one back end DBMS like mySQL or pgSQL then it's a no brainer to just implement ODBC and code up the necessary hooks, calls and lookups etc. But if flexibility to integrate different DBMS architectures are goals then you are right, something like ADOdb is the very way to go. I'm looking at OpenDBX for a work project, it'll probably be faster than ADOdb for somethings, but not sure it will add anything other than performance to the mix.

[tvdb-scott]

Rise from your grave, 18 month old thread.

Full discussion is more in-depth here:
http://forum.xbmc.org/showthread.php?tid=37449