On Jul 14, 2021, at 05:14, Alejandro olivan Alvarez
<alejandro.olivan.alva...@gmail.com> wrote:
> I have messed a little with rivendell database, quite successfully, but only
> for query/read operations ... altering/writing directly the database of such
> a complex application is for the brave :-)
Just to amplify Alejandro’s point: directly modifying the Rivendell database is
NOT A SUPPORTED METHOD for making changes in Rivendell! Specifically, the
database schema CAN and DOES change between different versions of Rivendell;
meaning that the update method that worked perfectly three months ago could end
up NUKING YOUR DATABASE next time around.
A much better and safer method for making these sorts of site-specific bulk
changes is to write a script that uses Rivendell’s WebAPI. See:
http://opsguide.rivendellaudio.org/apis/web_api.pdf
The Web API is a documented, public and above all stable interface; using it
will allow you to write scripts that won’t break across different versions of
Rivendell.
N.B. — If you insist on writing changes directly to the DB, be sure that you
have a known good backup of it first. The sanity and gray hair (not to mention
job) that you save may be your own.
Cheers!
|---------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|---------------------------------------------------------------------|
| Beware of Programmers who carry screwdrivers. |
| |
| -- Leonard Brandwein |
|---------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
