[01:25:49] if it doesn't support it why are there literally json commands in MariaDB? [01:26:50] Ugly hack [01:26:56] [1/5] I remember when I used to use things like [01:26:56] [2/5] ``` [01:26:56] [3/5] UPDATE mw_settings SET s_settings = JSON_INSERT(s_settings, '$.wmgDefaultRobotPolicy', JSON_EXTRACT(s_settings, '$.wgDefaultRobotPolicy')); [01:26:57] [4/5] ``` [01:26:57] [5/5] years ago and they definitely worked. (I pulled that from SAL) [01:28:33] It's not JSON support; sure, you can put JSON in there which is just an alias for text [01:28:53] You dont get any of the features that you get with a database that supports json [01:30:31] I guess technically setting a type to JSON is just setting it to longtext as an alias but that still shows the intent to support JSON IMO. [01:36:04] And IIRC wasnt there rational for just aliasing JSON as longtext is json is just text? That is kinda true lol. And it's slower to have true JSON db side anyway. [01:40:47] mariadb even does support adding a constraint to ensure json is valid (which we should do) [01:44:58] using the json type will automatically add that constraint too it seems. So could just switch to that... [08:14:04] [1/5] this really should not work [08:14:04] [2/5] ``` [08:14:04] [3/5] [blankeclair@mwtask181:~]$ curl -v https://awlibuwbfeuliwaefiuwaefiu.invalid [08:14:05] [4/5] * Trying [2606:4700::6812:7be]:443... [08:14:05] [5/5] ``` [13:55:17] ? [19:40:47] that domain should not resolve [20:22:45] computers are fucking weird