** Also affects: mythplugins (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I've noticed while trying to move recordings with mytharchive from myth
0.21 to 0.22, that the the cutlists and adverts were not being imported
to the new version.
The log would terminate with the following error:
{{{
2009-11-21 12:03:54.058 Inserted recorded details into database
2009-11-21 12:03:54.060 DB Error (recordedmark insert):
Query was:
INSERT INTO recordedmarkup (chanid, starttime, mark, offset,
type)VALUES(?,?,?,?,?);
Bindings were:
:CHANID=1003, :MARK=0, :OFFSET=, :STARTTIME=2009-09-20T20:00:00, :TYPE=-3
No error type from QSqlError? Strange...
QSqlDatabasePrivate::removeDatabase: connection 'DBManager0' is still in use,
all queries will cease to work.
}}}
I then made a new recording, ran mythcommflag and created a editing
cutlist. Once done, I exproted the new recording, deleted the origional,
and then imported it again. There were no advert or cut marks in the
imported file.
Comparing the old (0.21) and new (0.22) .xml files, I noticed that the
recordedmarkup table entries were not present in the exported files.
On checking the mysql database, I noticed that the columns in
recordedmarkup tables are different between the two mythtv versions:
specifically the "offset" column is now called "data" in the new
version.
Here's an extract from the file which created the new database in myth
0.22:
{{{
DROP TABLE IF EXISTS `recordedmarkup`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `recordedmarkup` (
- `chanid` int(10) unsigned NOT NULL DEFAULT '0',
- `starttime` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
- `mark` mediumint(8) unsigned NOT NULL DEFAULT '0',
- `type` tinyint(4) NOT NULL DEFAULT '0',
- `data` int(11) unsigned DEFAULT NULL,
- PRIMARY KEY (`chanid`,`starttime`,`type`,`mark`)
+ `chanid` int(10) unsigned NOT NULL DEFAULT '0',
+ `starttime` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
+ `mark` mediumint(8) unsigned NOT NULL DEFAULT '0',
+ `type` tinyint(4) NOT NULL DEFAULT '0',
+ `data` int(11) unsigned DEFAULT NULL,
+ PRIMARY KEY (`chanid`,`starttime`,`type`,`mark`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
}}}
The old version (0.21) was:
{{{
- `offset` varchar(32) default NULL,
+ `offset` varchar(32) default NULL,
}}}
Looks like a deliberate change to me...
Nuvexport .sql files will import the recordedmarkup data correctly ONLY
IF the file is edited to change the "offset" entry to read "data"
instead. (using: "mysql -u mythtv -p mythconverg < *.sql")
I could not get mytharchive to import recordedmarkups correctly, even
after editing the .xml file.
My guess is that either the mapping in mytharchive doesn't take the
changes into consideration, or that the new myth version 0.22 is
creating the table incorrectly.
- I'm an Ubuntu Karmic user.
+ I'm an Ubuntu Karmic xa6_64 user.
+ mytharchive_0.22.0+fixes22594-0ubuntu1_amd64.deb is installed.
I've reported this at the mythtv bugtracker as well.
(http://cvs.mythtv.org/trac/ticket/7626)
Thanks,
David
** Description changed:
I've noticed while trying to move recordings with mytharchive from myth
0.21 to 0.22, that the the cutlists and adverts were not being imported
to the new version.
The log would terminate with the following error:
{{{
2009-11-21 12:03:54.058 Inserted recorded details into database
2009-11-21 12:03:54.060 DB Error (recordedmark insert):
Query was:
INSERT INTO recordedmarkup (chanid, starttime, mark, offset,
type)VALUES(?,?,?,?,?);
Bindings were:
:CHANID=1003, :MARK=0, :OFFSET=, :STARTTIME=2009-09-20T20:00:00, :TYPE=-3
No error type from QSqlError? Strange...
QSqlDatabasePrivate::removeDatabase: connection 'DBManager0' is still in use,
all queries will cease to work.
}}}
I then made a new recording, ran mythcommflag and created a editing
cutlist. Once done, I exproted the new recording, deleted the origional,
and then imported it again. There were no advert or cut marks in the
imported file.
Comparing the old (0.21) and new (0.22) .xml files, I noticed that the
recordedmarkup table entries were not present in the exported files.
On checking the mysql database, I noticed that the columns in
recordedmarkup tables are different between the two mythtv versions:
specifically the "offset" column is now called "data" in the new
version.
Here's an extract from the file which created the new database in myth
0.22:
{{{
DROP TABLE IF EXISTS `recordedmarkup`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `recordedmarkup` (
`chanid` int(10) unsigned NOT NULL DEFAULT '0',
`starttime` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`mark` mediumint(8) unsigned NOT NULL DEFAULT '0',
`type` tinyint(4) NOT NULL DEFAULT '0',
`data` int(11) unsigned DEFAULT NULL,
PRIMARY KEY (`chanid`,`starttime`,`type`,`mark`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
}}}
The old version (0.21) was:
{{{
`offset` varchar(32) default NULL,
}}}
Looks like a deliberate change to me...
Nuvexport .sql files will import the recordedmarkup data correctly ONLY
IF the file is edited to change the "offset" entry to read "data"
instead. (using: "mysql -u mythtv -p mythconverg < *.sql")
I could not get mytharchive to import recordedmarkups correctly, even
after editing the .xml file.
My guess is that either the mapping in mytharchive doesn't take the
changes into consideration, or that the new myth version 0.22 is
creating the table incorrectly.
- I'm an Ubuntu Karmic xa6_64 user.
+ I'm an Ubuntu Karmic x86_64 user.
mytharchive_0.22.0+fixes22594-0ubuntu1_amd64.deb is installed.
I've reported this at the mythtv bugtracker as well.
(http://cvs.mythtv.org/trac/ticket/7626)
Thanks,
David
--
Mytharchive (myth 0.22 karmic) fails to import/export recordedmarkup
https://bugs.launchpad.net/bugs/486233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
