[mythtv-users] Okay adding primary key to mythconverg tables that don't have them?

[stinga]

On 20/02/18 07:16, James Purl wrote:
> I was considering moving my mythconverg DB into a MySQL cluster using 
> the group replication plugin 
> <https://dev.mysql.com/doc/refman/5.7/en/group-replication.html>, but 
> some of the tables don't have primary keys--among the requirements 
> <https://dev.mysql.com/doc/refman/5.7/en/group-replication-requirements.html> for 
> group replication. I was considering altering those tables to just add 
> an auto_increment primary key. Does anyone know if these modifications 
> might break future schema upgrades? Not asking to predict the future, 
> but if anyone knows if the typical changes done to the DB schema would 
> conflict. I also understand I'd be on my own if this causes me a mess.
>
I am not a dev and my crystal ball is in for it's 100 year service. :-)

Basically the `Does anyone know if these modifications might break 
future schema upgrades?` question can't be answered.
Depends on what the dev do. As you said, we can't predict the future. 
Also adding what is a new index may slow queries down. (or make it 
better <shrug>)

Any reason for using group replication instead of just replication? (oh, 
cluster).
One thing I have seen is that devs have thought about not using mysql in 
the future, or an embedded version (or something), I hope they don't as 
my mysql DB is on another host anyway.

-- 
'ooroo

Stinga...(:)-)
---------------------------------------------------
Email: stinga+mythtv at wolf-rock.com  o
You need only two tools.        o /////
A hammer and duct tape. If it    /@   `\  /) ~
doesn't move and it should use  >  (O)  X<  ~  Fish!!
the hammer. If it moves and      `\___/'  \) ~
shouldn't, use the tape.           \\\
---------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180221/7627dcf2/attachment.html>