Notices tagged with innodb
-
@xrevan86 @clacke Years ago, #InnoDB was produced by an independent company, just as #Sleepycat (BerkeleyDB ... BDB engine) was. I don't know if it was possible to use InnoDB separately from #MySQL even then. #Oracle bought Sleepycat and then Inno, and finally #Sun.
I've been using it for somewhere around 20 years (+/-2 years), having encountered it in a college course (replacing Hughes #MiniSQL).
-
@xrevan86 @clacke Years ago, #InnoDB was produced by an independent company, just as #Sleepycat (BerkeleyDB ... BDB engine) was. I don't know if it was possible to use InnoDB separately from #MySQL even then. #Oracle bought Sleepycat and then Inno, and finally #Sun.
I've been using it for somewhere around 20 years (+/-2 years), having encountered it in a college course (replacing Hughes #MiniSQL).
-
@pskosinski@quitter.no Regarding your #Unicode problems in !gnusocial at http://status.hackerposse.com/url/6778 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 c…
-
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).
-
#Quitter.is was down since #MariaDB for #Debian #wheezy didn't include #InnoDB support despite having such config options in my.cnf