On Thursday 2017-01-12 17:21:05 Alan Brown wrote:
> On 12/01/17 14:14, Josip Deanovic wrote:
> > So if one is for some reason locked to specific old version of a
> > specific old proprietary application one can't do much than continue
> > with the MyISAM as innodb is not an option and external sear
On 12/01/17 14:14, Josip Deanovic wrote:
> So if one is for some reason locked to specific old version of a
> specific old proprietary application one can't do much than continue
> with the MyISAM as innodb is not an option and external search engines
> are not supported either.
I've had to deal w
On Thursday 2017-01-12 08:36:53 Phil Stracchino wrote:
> Most applications that "require" MyISAM "require" it for no good reason,
> or depend on features that have historically been supported only by
> MyISAM but are now supported in InnoDB in current MySQL releases. It
> bears case-by-case examin
On 01/12/17 00:22, Josip Deanovic wrote:
> On Wednesday 2017-01-11 17:43:42 Phil Stracchino wrote:
> [...]
>> The truth is, MyISAM pretty much sucks and you shouldn't be using it in
>> production any more. Remember that MyISAM is a 20-year-old storage
>> engine, one of whose primary design criteri
On Wednesday 2017-01-11 17:43:42 Phil Stracchino wrote:
[...]
> The truth is, MyISAM pretty much sucks and you shouldn't be using it in
> production any more. Remember that MyISAM is a 20-year-old storage
> engine, one of whose primary design criteria was that it needed to work
> *acceptably well*
On 01/11/17 17:43, Phil Stracchino wrote:
>
> You may want to use 2 if there are no InnoDB tables *outside of the
> MySQL schema*, because in most
...oops. That paragraph was meant to continue: "..in most cases, the
MyISAM tables inside the mysql schema change only rarely and you are
unlikely t
On 01/11/17 16:57, scar wrote:
> i have been using the script at [1] but then i noticed that the
> incremental backups were quite large and containing some MYD and MYI
> files. so i realized these were myisam databases. i read that the best
> way to backup both innodb and myisam databases was
i have been using the script at [1] but then i noticed that the
incremental backups were quite large and containing some MYD and MYI
files. so i realized these were myisam databases. i read that the best
way to backup both innodb and myisam databases was to use the mysqldump
option --lock-tab
