Hi,
There are quite a few different database issues with Rivendell where
older versions of MySQL implied NULL values or converted NULL dates to
0000-00-00 00:00:00 but with MySQL v5.7 you can't do that any more (at
best 0000-00-00 gives you an invalid date error).
I assumed it was only when creating a new database but it makes sense
all logs have the same problem. I will have to go through the code for
logs because just doing a quick test I have issues with a few fields in
LOGS and the blah_LOG table you create if you make a new "blah" log.
Looking at the structure of the tables, this might also give errors when
dealing with DATE and DATETIME fields all across the Rivendell database
so quite a lot to track down I guess.
More things for the github issues page either way.
I also can't figure out why qtconfig doesn't seem to change the look and
feel of Rivendell at all but thats a problem for another day.
Regards,
Wayne
On 27/05/16 12:51, Manuel wrote:
Wayne Merricks <waynemerricks@...> writes:
Polymer isn't easy to get hold of, it was last updated in 2005 I think.
When you try to compile it under Xenial, you get an error missing
lqt-mt. This used to be part of the libqt3-mt-dev package but I can't
find it at the moment for Ubuntu.
Don't worry, Wayne. I decided to wait for more stability on this subject.
I've just discovered that I cannot add logs. For every one I try to add it
says "Log Already Exists!".
I'll keep on using v2.10.3 on other machine.
Thanks for everything.
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
