Notices tagged with mysql, page 2
-
so bumping up shmmax does not seem to allow #mysql to use more RAM. Other than use $RDMS or $OS, anybody got any ideas? #Linux
-
Why is #MySQL skipping 7? I get why 6 is being skipped, but why 7?
-
Anybody have #mysql upgrade repo instructions for #CentOS6 that don't involve remi? remi had a bad PHP issue this summer, so now people are skittish. #RHEL6 has their #RHEL collections, but I need something specific to #CentOS 6. I know *I* could recompile or use the MySQL community repos, but those aren't going to work for everyone. The MySQL community instructions might work for this other person. I need to check.
Also, is there a mysql !fediverse !fedgroups ?
-
Anybody have a recommended version of #MySQL/#MariaDB for performance purposes?
-
will
SELECT DISTINCT * INTO TableA_Verify FROM TableA;
only work on certain versions of #mysql because I keep getting an undeclared variable, but the table is definitely there.
-
I have zero experience with stored procedures. How would I tell if there are any for #Postgres and #MySQL?
-
Is there a way to write a query that bypasses the query log in #MySQL? Something very strange is going on.
-
Is it possible to do a WHERE clause based on type. It seems like that should be the case and I'm just doing something wrong. #MySQL
-
Thought I'd install #VirtualMin, but it ate my #MariaDB setup, tried to replace it with #MySQL, botched the installation, and I had to recover it all manually. Killed my !StatusNet daemons, had to #KickTheDaemons. Sorry for the interrupted service. !SysAdmin #Fail.
-
@jaywink@iliketoast.net That is *very* bad news. I switched completely to #MariaDB because #Oracle was making proprietary-like moves with #MySQL. In one step, MariaDB Corp has leapfrogged Oracle. I won't say they've gone #evil yet, but this is definitely not a positive development.
-
@mikael Thanks for pushing + helping out to find some deficiencies! Thanks to this we'll get proper constraints (I thought #mysql simply sucked at that department).
-
@maiyannah @moonman Because #MySQL (and #MariaDB) sucks and the only reason people still use it is because of legacy? :)
#Postgres beats the crap out of it any day.
-
Unlearning #MySQL to get used to #PostgreSQL takes some getting used to. I need it for #PostGIS, which just adds another mental level to the effort of reading documentation. But I guess it's worth it in the end!
-
@mk After a lot of futzing around with phpMyAdmin I followed one suggestion I found: stopped #mySQL and made a backup of the database *files* (simple local rsync), then UNinstalled phpMyAdmin. Planning toe-install it I noticed ASUSTOR's App Central also has something called SQL Buddy - so I installed that. And it let me log in without any problem. It's simple. It works. That's all I need. I supect #phpMyAdmin has just become more and more complex to the point where it's become fragile... So it's #SQLBuddy for now. Dropping the 'pspmyadmin' database... #nas
-
Due to the way #SSL implemented in #MySQL, downgrade and #MITM possible with all versions. Affects #MariaDB also, though they are patching 10.1.x (and possibly 10.0.x and 5.5.x). *Patches may break existing applications that depend on prior behavior* See: http://url.federati.net/PFYrj
-
Due to the way #SSL implemented in #MySQL, downgrade and #MITM possible with all versions. Affects #MariaDB also, though they are patching 10.1.x (and possibly 10.0.x and 5.5.x). *Patches may break existing applications that depend on prior behavior* See: http://url.federati.net/PFYrj
-
@thelovebug #StatusNet discards 4 byte UTF-8 characters (actually it's #MySQL which has incomplete Unicode support in 'utf8' tables). It's fixed in !gnusocial v1.2.x (upgrade script converts tables to utf8mb4)
-
@pskosinski@quitter.no Regarding your #Unicode problems in !gnusocial at https://quitter.no/notice/271149
We have actually, in the current nightly branch, made the necessary changes to support UTF-8 properly. The problem is #MySQL encoding support ("utf8" != UTF-8) and limited indexing lengths in #InnoDB (making 191 characters the most when using 4 byte unicode characters).
If one wants to support proper UTF-8 in #MySQL the tables and columns need to be defined as #utf8mb4 instead of #utf8. And #Vinilox hasn't upgraded yet :D
-
I pushed a fix, assuming you don't have URLs there that are >191 characters long. (that really needs to be fixed, but #MySQL - more specifically #InnoDB - sucks).
-
this is because (y)our #mysql has the "wrong" encoding, it's not really utf8. !gnusocial might fix that one day by converting the mysql to the correct encoding