That was one of my thoughts, but when I checked the Rivendell tables in MySQL, they are all MyISAM.
Although I do think it is something with the DB, when I start rdlogmanager from the command line and try changing a clock, I see a MySQL error like thus: invalid SQL or failed DB connection[Table 'Rivendell.event2_POST' doesn't exist QMYSQL3: Unable to execute query]: select `event2_POST`.ID,`event2_POST`.CART_NUMBER,`event2_POST`.START_TIME,`event2_POST`.TIME_TYPE,`event2_POST`.TRANS_TYPE,`event2_POST`.START_POINT,`event2_POST`.END_POINT,`event2_POST`.SEGUE_START_POINT,`event2_POST`.SEGUE_END_POINT,CART.TYPE,CART.GROUP_NAME,CART.TITLE,CART.ARTIST,CART.ALBUM,CART.YEAR,CART.LABEL,CART.CLIENT,CART.AGENCY,CART.USER_DEFINED,CART.CONDUCTOR,CART.SONG_ID,CART.FORCED_LENGTH,CART.CUT_QUANTITY,CART.LAST_CUT_PLAYED,CART.PLAY_ORDER,CART.ENFORCE_LENGTH,CART.PRESERVE_PITCH ,`event2_POST`.TYPE,`event2_POST`.COMMENT,`event2_POST`.LABEL,`event2_POST`.GRACE_TIME,`event2_POST`.POST_POINT,`event2_POST`.SOURCE,`event2_POST`.EXT_START_TIME,`event2_POST`.EXT_LENGTH,`event2_POST`.EXT_DATA,`event2_POST`.EXT_EVENT_ID,`event2_POST`.EXT_ANNC_TYPE,`event2_POST`.EXT_CART_NAME,CART.ASYNCRONOUS,`event2_POST`.FADEUP_POINT,`event2_POST`.FADEUP_GAIN,`event2_POST`.FADEDOWN_POINT,`event2_POST`.FADEDOWN_GAIN,`event2_POST`.SEGUE_GAIN,CART.PUBLISHER,CART.COMPOSER,CART.USAGE_CODE,CART.AVERAGE_SEGUE_LENGTH,`event2_POST`.LINK_EVENT_NAME,`event2_POST`.LINK_START_TIME,`event2_POST`.LINK_LENGTH,`event2_POST`.LINK_ID, `event2_POST`.LINK_EMBEDDED,`event2_POST`.ORIGIN_USER,`event2_POST`.ORIGIN_DATETIME,CART.VALIDITY, `event2_POST`.LINK_START_SLOP,`event2_POST`.LINK_END_SLOP, `event2_POST`.DUCK_UP_GAIN,`event2_POST`.DUCK_DOWN_GAIN,CART.START_DATETIME,CART.END_DATETIME,`event2_POST`.EVENT_LENGTH,CART.USE_EVENT_LENGTH,CART.NOTES from `event2_POST` left join CART on `event2_POST`.CART_NUMBER=CART.NUMBER order by COUNT I am thinking that something is not getting updated in the database the way it should when rdadmin runs after installing 2.9.0 Lorne Tyndale > -------- Original Message -------- > Subject: Re: [RDD] Potential_bug_in_rdlogmanager_when_creating_a_new > _clock? > From: Wayne Merricks <[email protected]> > Date: Mon, July 14, 2014 5:33 pm > To: <[email protected]> > > > Hi, > > Is this the ago old MyISAM vs InnoDB thing rearing its head? I didn't > think it was possible for a schema update to change the DB Engine but I > suppose its possible to do so. > > On 2014-07-14 17:53, Lorne Tyndale wrote: > > Hi, > > > > I ran into a potential bug in rdlogmanager when creating a clock / > > adding events to a clock in Rivendell 2.9.0 > > > > For some reason it will only let me add 1 single event to a clock. > > Clocks previously created seem okay. > > > > However when creating a new clock, or adding events to an old clock, > > it > > will only save the most recent change / addition, and it blanks out > > all > > other events in the clock. > > > > Just to check, I rolled back to 2.8.1 (rolled back the DB from a > > backup) > > and tried the same - and did not experience this difficulty. > > > > Can anyone else confirm this behaviour in 2.9.0, or is it just me? > > > > I'm running on Ubuntu 10.04 and compiled from source. > > > > Thanks, > > > > Lorne Tyndale > > > > _______________________________________________ > > Rivendell-dev mailing list > > [email protected] > > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
