I don't have an answer for your problem, but regarding MySQL indexes, that should not be a problem. Databases are supposed to work properly even when indexes are missing. The only drawback are performance issues, when trying to sort, or fetching a specific row in the table, based on that column (e.g. "WHERE col_name > value")
UNIQUE constraints are a subclass of indexes, but these are explicitly defined at table creation (or later, for that matter), and if they are missing, you will simply risk having multiple inserts for the same values (might be bad for a Rivendell log, but MySQL will definitely not complain). I am not sure how the mysql library works this out, but I think the multiple inserts with the same ID are due to the SQL command or library failing to execute, then the log manager skips to the next one, to finally quit due to errors... This is a blind guess, but is it possible that you upgraded Rivendell without upgrading the database? _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
