[mythtv] Any thoughts about database transparency?

aaron aiperl at rogers.com
Mon Jul 7 21:01:01 EDT 2003


On Mon, 7 Jul 2003 14:47:37 -0400 spake Joseph of:

> > -----Original Message-----
> > From: mythtv-dev-bounces at snowman.net
> > [mailto:mythtv-dev-bounces at snowman.net]On Behalf Of Kevin J. Slater
> > Sent: Monday, July 07, 2003 2:08 PM
> > To: mythtv-dev at snowman.net
> > Subject: [mythtv] Any thoughts about database transparency?
> >
> >
> > Has anyone given thought to how database transparent MythTV is? I
> > don't want to
> > start a religious war, but was wondering how hard it would be to get Myth
> > working with PostgreSQL? (Flame me directly if you must.)
> 
> Any database supported by Qt should work.  However, the Myth source would
> have to be tweaked to allow for selection of a database driver.  Currently,
> the name of the database driver is hard-coded in a handful of places.
> 
> From the Qt 3.1.2 reference documentation:
> 
> 	 "The currently available drivers are:
> 
> 	    * QODBC3 - ODBC (Open Database Connectivity) Driver
> 	    * QOCI8 - Oracle Call Interface Driver
> 	    * QPSQL7 - PostgreSQL v6.x and v7.x Driver
> 	    * QTDS7 - Sybase Adaptive Server and Microsoft SQL Server Driver
> 	    * QMYSQL3 - MySQL Driver
> 
> 	Note that additional 3rd party drivers can be loaded dynamically. "


I had toyed with the idea of trying to get Myth to work with DB2 a few months
ago, when a soundcard driver bug was causing my database to be lost every
other day (Mysql has no crash recovery capabilities, it seems). But then I got
lazy (and the bug got fixed). :)

aaron


More information about the mythtv-dev mailing list