[mythtv] Renewing PostgreSQL support

[Per Heldal]

On 22/06/10 03:07, Ross Campbell wrote:
> Surely I can't be the only one who uses phpmyadmin for all sorts of
> data management in mythtv -- from managing channel lineup table
> changes, to changing metadata by hand, etc. I really appreciate the
> ability to access the mythconverg database via sql.


I try to avoid muckin' about with the DB, but there's at least 3 tasks
that currently require manual intervention for me (using DVB-S2).

1. One initial (seed) transponder has to be added manually to an empty
database to be able to scan a satellite position. ("Add transport" is
non-functional in mythtv-setup in trunk).

2. The majority of the 200-300 channels returned by a scan are either
junk (of no interest) or not included in my subscription. To edit and
set these invisible with mythtv-setup would take forever. I know
channels can be hidden from mythweb, but right now in trunk it only
displays visible channels so (re)enabling visibility for a channel to
correct a mistake is not an option in mythweb.

3. Mythtv-setup is only able to find and download icons for a small
fraction (<5%) of the available channels. I've found it much simpler to
maintain my own set of channel icons (from sources like lyngsat.com) and
cut-paste paths into the channel-table with some grid-view table-browser
for the few channels I keep as visible.


That said, I do agree with the devs that the DB should be kept internal
to mythbackend, but I'd prefer proper front-backend separation
(documented protocol with client-access-libraries) with mythfrontend as
a reference DB-less client-implementation. This is no trivial change
though ;)


//per