15 Jan
2014
15 Jan
'14
2:43 p.m.
Le 2014-01-15 06:40, Michal Čihař a écrit :
Hi
Dne Wed, 15 Jan 2014 06:25:20 -0500
Marc Delisle <marc(a)infomarc.info> napsal(a):
Just to clarify, you are fine with removing for export?
--
Marc Delisle
http://infomarc.info | http://phpmyadmin.net
Le 2014-01-15 03:01, Michal Čihař a écrit :
There is simple workaround - use different tool to uncompress the
backup.
Hi
Dne Tue, 14 Jan 2014 10:57:40 -0500
Marc Delisle <marc(a)infomarc.info> napsal(a):
Well I do, as the person who created the ticket, who could not restore
his backup. I had a look at this bug [0]. Not being able to
completely import a .bz2
file is serious.
Given that the bug was not discovered for about ten years, I don't see
it that serious. But the fact that we did not get a report about
this, might mean that
this feature is not used much.
Indeed, that's also possibility.
Users who want compression can use the gzip
option, so removing bz2
would not leave them with nothing.
I'm fine with removal (for export, for import, it should IMHO stay for
a while). bz2 really does not have much benefits these days