| Tuesday, July 7th, 2020, 00:23 UTC | ||
| [00:23:09] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has quit (Read error: Connection reset by peer) | |
| [00:28:15] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has joined #mythtv | |
| [00:28:15] | Mode for #mythtv by ChanServ!ChanServ@services. : +v markspieth | |
| [01:01:04] | blahdodo (blahdodo!~blahdodo@69.172.190.84) has quit (Ping timeout: 246 seconds) | |
| [01:15:44] | blahdodo (blahdodo!~blahdodo@69.172.190.84) has joined #mythtv | |
| [02:03:53] | ooshlablu (ooshlablu!~ooshlablu@2601:18d:4600:43f0:546f:5b98:fe5a:4cde) has quit (Remote host closed the connection) | |
| [02:04:51] | ooshlablu (ooshlablu!~ooshlablu@98.217.124.239) has joined #mythtv | |
| [03:22:52] | Warped (Warped!~Warped@unaffiliated/warped) has joined #mythtv | |
| [04:24:49] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has quit (Read error: Connection reset by peer) | |
| [04:28:45] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has joined #mythtv | |
| [04:28:46] | Mode for #mythtv by ChanServ!ChanServ@services. : +v markspieth | |
| [06:47:17] | Steve-Goodey (Steve-Goodey!~steve@2a00:23c5:7d83:6501:6032:9caa:16d4:6ffa) has joined #mythtv | |
| [06:47:17] | Mode for #mythtv by ChanServ!ChanServ@services. : +v Steve-Goodey | |
| [06:50:00] | peterbennett (peterbennett!~pi@mythtv/developer/peterbennett) has quit (Quit: WeeChat 2.3) | |
| [06:51:50] | peterbennett (peterbennett!~pi@mythtv/developer/peterbennett) has joined #mythtv | |
| [06:51:50] | Mode for #mythtv by ChanServ!ChanServ@services. : +v peterbennett | |
| [08:28:30] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has quit (Ping timeout: 245 seconds) | |
| [08:29:44] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has joined #mythtv | |
| [08:29:44] | Mode for #mythtv by ChanServ!ChanServ@services. : +v markspieth | |
| [09:26:50] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has quit (Ping timeout: 245 seconds) | |
| [09:29:44] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has joined #mythtv | |
| [09:29:44] | Mode for #mythtv by ChanServ!ChanServ@services. : +v markspieth | |
| [10:15:46] | Steve-Goodey (Steve-Goodey!~steve@2a00:23c5:7d83:6501:6032:9caa:16d4:6ffa) has quit (Quit: Konversation terminated!) | |
| [13:10:41] | Steve-Goodey (Steve-Goodey!~steve@2a00:23c5:7d83:6501:6032:9caa:16d4:6ffa) has joined #mythtv | |
| [13:10:41] | Mode for #mythtv by ChanServ!ChanServ@services. : +v Steve-Goodey | |
| [15:40:50] | SteveGoodey (SteveGoodey!~steve@host86-149-198-216.range86-149.btcentralplus.com) has joined #mythtv | |
| [15:40:51] | Mode for #mythtv by ChanServ!ChanServ@services. : +v SteveGoodey | |
| [18:55:37] | bill6502 (bill6502!~bill@205.178.24.168) has joined #mythtv | |
| [19:08:40] | bill6502: | In order to fix #13577 (CHARACTER SET default->utf8) for users with up-to-date <plugin>DBSchemaVers I need to recap the earlier changes, |
| [19:08:40] | ** MythLogBot https://code.mythtv.org/trac/ticket/13577 ** | |
| [19:08:50] | bill6502: | but that will cause a DB update, which isn't normally allowed. Any opinions about doing this (it only affects schemas for |
| [19:09:07] | bill6502: | archive, game, music and weather |
| [19:09:21] | bill6502: | any opinions about allowing it? |
| [19:21:25] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has quit (Ping timeout: 245 seconds) | |
| [19:21:35] | markspieth (markspieth!~yaaic@mythtv/developer/markspieth) has joined #mythtv | |
| [19:21:35] | Mode for #mythtv by ChanServ!ChanServ@services. : +v markspieth | |
| [19:25:33] | gregbert (gregbert!~gregbert@unaffiliated/gregbert) has joined #mythtv | |
| [19:36:36] | peterbennett: | bill6502: First, thanks for fixing the schma vers for the bindings, which I forgot with my schema update. |
| [19:38:17] | peterbennett: | bill6502: I assume you need a schema change for fixes/31 ? |
| [19:42:15] | peterbennett: | bill6502: if the previous schema update failed, fixing the code should be all that is needed. Maybe no need to introduce a new schema version. |
| [19:43:31] | peterbennett: | bill6502: Then after installing the fixed code, the schema update would be done successfully, if the failed schema update did not update the schema version number. |
| [19:44:43] | bill6502: | peterbennett: The concern is that someone who has already up to date ('cause there weren't on MySQL v8) will still have the "default" CHARACTER SETs. And v8 needs to have them = :utf8". |
| [19:45:49] | bill6502: | s/who has already up to date/who is already up to date/ |
| [19:46:34] | bill6502: | grrr: s/:utf8"/"utf8" |
| [19:47:40] | peterbennett: | bill6502: So somebody may have upgraded to V31 on earlier MYSQL then upgrades to MYSQL 8 and everything falls apart? |
| [19:53:12] | peterbennett: | I don't really understand why the database does not always use UTF8. |
| [19:54:09] | peterbennett: | Howevere, I suppose if you applied teh patch at least those people who are struggling to update will be OK, only those still on earlier mysql may be affected in the future. |
| [19:54:17] | peterbennett: | At least it helps some people. |
| [20:15:04] | bill6502: | peterbennett: to your 1st point, I haven't seen any breakage. It's just that we'd have some users on CHARACTER SETs that were different, at least in name. |
| [20:15:18] | bill6502: | peterbennett: re UTF8, it gets worse. At some <unknown> time in the future, MySQL says UTF8 (currently an alias for UTF8MB3) will become an alias for UTF8MB4. 3 bytes to 4 in storage. |
| [20:18:20] | bill6502: | Maybe everything should be converted to UTFMB4 now. But that's another story. And from what I've read, it's not a simple process. |
| [20:39:19] | stuarta: | charset issues are a pain in the arse |
| [20:40:00] | stuarta: | peterbennett: to your point about what charset we use, it's always been "default". ie. we've taken whatever the db engine is configured, and now they've changed the default |
| [20:44:34] | brfransen (brfransen!~brfransen@097-095-233-051.res.spectrum.com) has joined #mythtv | |
| [20:47:32] | stuarta: | one of the major pains in my practice attempts at doing a trac -> redmine migration have been dealing with charset differences |
| [20:57:31] | peterbennett: | stuarta: I just create a database and don't worry about charset. Have I set myself up for problems? |
| [21:06:29] | bill6502: | Back in 2008, mc.sql was switched from latin1 to utf8: ALTER DATABASE mythconverg DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci; |
| [21:09:21] | stuarta: | peterbennett: since you are based in the US, it's unlikely you use any characters from the extended charsets which can be/are interpreted differently by different charsets |
| [21:17:48] | stuarta: | i only noticed it in old tickets which contained nordic languages |
| [21:17:49] | jheizer: | Looks like I have a mix of latin1 and utf8 on a rather old DB. |
| [21:20:11] | stuarta: | yay, got netdata to feed data from an internal only server, to a central collector |
| [21:23:50] | bill6502: | peterbennett: this displays my default character sets: SELECT SCHEMA_NAME,DEFAULT_CHARACTER_SET_NAME FROM information_schema.SCHEMATA; my mythconverg is utf8 |
| [21:24:05] | bill6502: | jheizer: what did you do to look at all tables? |
| [21:24:54] | stuarta: | jheizer: same here |
| [21:25:08] | stuarta: | bill6502: you can grep a backup for CHARACTER SET |
| [21:25:21] | stuarta: | or you can do a mysqldump with |
| [21:25:25] | ** stuarta finds option ** | |
| [21:26:29] | stuarta: | --no-data |
| [21:26:55] | stuarta: | to get a "schema only" backup file |
| [21:27:15] | jheizer: | bill6502: I just did "show full columns from XYZ" on a few random tables |
| [21:27:38] | peterbennett: | That select also gives me utf8 for my test mythdb |
| [21:27:58] | stuarta: | also "show create table <xx>\G |
| [21:28:00] | stuarta: | " |
| [21:28:23] | peterbennett: | Also on my prod |
| [21:28:39] | jheizer: | mayjority of the ones I peaked at were utf8 |
| [21:28:59] | stuarta: | grep'n the backup gives you all variants |
| [21:29:42] | jheizer: | recently restored to a new VM on mysql 5.7.30 |
| [21:43:20] | bill6502: | SELECT TABLE_SCHEMA,TABLE_NAME,TABLE_COLLATION FROM INFORMATION_SCHEMA.`TABLES` WHERE TABLE_SCHEMA='mythconverg'; |
| [21:43:55] | bill6502: | Where: "because the first part of collation includes the charset" |
| [21:44:29] | bill6502: | all utf8_.... but 4 are: latin1_swedish_ci |
| [21:54:28] | bill6502: | And for individual columns (that aren't utf8): SELECT TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME,CHARACTER_SET_NAME FROM INFORMATION_SCHEMA.`COLUMNS` WHERE TABLE_SCHEMA='mythconverg' AND CHARACTER_SET_NAME != 'utf8'; |
| [21:55:20] | stuarta: | messy ain't it? |
| [21:55:54] | ** stuarta observes theme packaging being done on the VM on the osuosl openstack cluster ** | |
| [21:56:32] | bill6502: | i believe your initial comment when i 1st asked was something like "ugh". i agree |
| [21:56:38] | stuarta: | :) |
| [21:57:03] | stuarta: | it's downright nasty |
| [22:07:37] | Steve-Goodey (Steve-Goodey!~steve@2a00:23c5:7d83:6501:6032:9caa:16d4:6ffa) has quit (Quit: Konversation terminated!) | |
| [22:27:37] | SteveGoodey (SteveGoodey!~steve@host86-149-198-216.range86-149.btcentralplus.com) has quit (Quit: Konversation terminated!) | |
| [22:51:17] | warpme_ (warpme_!uid391875@gateway/web/irccloud.com/x-erneqxdbgogtremw) has quit (Ping timeout: 260 seconds) | |
| [22:52:34] | afisher (afisher!sid188203@gateway/web/irccloud.com/x-dzvlweujdjyvuisn) has quit (Ping timeout: 256 seconds) | |
| [22:52:35] | jya (jya!sid396171@gateway/web/irccloud.com/x-egmikprhuyyuskth) has quit (Ping timeout: 272 seconds) | |
| [23:17:50] | peper03 (peper03!~peper03@mythtv/developer/peper03) has joined #mythtv | |
| [23:17:50] | Mode for #mythtv by ChanServ!ChanServ@services. : +v peper03 | |
| [23:19:01] | stuarta: | well there you go. the unzip code we imported back in 2010, remains fundamentally unchanged since then, apart from a few tidy up type commits |
| [23:21:13] | peper03_ (peper03_!~peper03@mythtv/developer/peper03) has quit (Ping timeout: 264 seconds) | |
IRC Logs collected by
BeirdoBot.
Please use the above link to report any bugs.