Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bzip2 export cannot be directly imported #10609

Closed
pma-import opened this issue Jan 7, 2014 · 12 comments
Closed

Bzip2 export cannot be directly imported #10609

pma-import opened this issue Jan 7, 2014 · 12 comments
Labels
Bug A problem or regression with an existing feature
Milestone

Comments

@pma-import
Copy link

When importing sql files from a phpMyAdmin export, bzip2 doesn't import all the data. Uncompressed, zip and gzip seem to work, but bzip2 only imports 188 rows from 1408. Comparing the file from the bzip2 with the uncompressed shows an identical file, so I'm guessing something has gone wrong on the import.

There was a problem on 4.1.2 with imports as well (no queries were run when importing bzip2) but this seems to be working better (although not perfectly) under 4.1.3

PHP: 5.5.7
MySQL: 5.6.15
CentOS 6.5


@pma-import
Copy link
Author

Issue exists in 4.1.4 also.


  • Original author: noodlesnz

@pma-import
Copy link
Author

I made some tests under two differents PHP versions and I get the same result: at some point during the import, the feof() command returns true, meaning that we have reached end of file, but we haven't reached it yet.


  • Original author: lem9

@pma-import
Copy link
Author

  • assigned_to: Marc Delisle

  • Original author: lem9

@pma-import
Copy link
Author

  • assigned_to: Marc Delisle --> nobody

  • Original author: lem9

@pma-import
Copy link
Author

  • assigned_to: Marc Delisle

  • Original author: lem9

@pma-import
Copy link
Author

For export files reaching a certain size (I tested with the sakila sample database, film table), there is an incompatibility between the bzip2 file produced by phpMyAdmin, and the bzread() function used to uncompress it at import time.

I found a workaround: decompress and recompress the file; for example:
bunzip2 film.sql.bz2
bzip2 film.sql
Then phpMyadmin has no problem to import. Nick, please confirm with your own file.


  • Original author: lem9

@pma-import
Copy link
Author

Also, with this in my configuration file:

$cfg['CompressOnFly'] = false;

I don't have the problem.


  • Original author: lem9

@pma-import
Copy link
Author

I can confirm that decompressing the file and recompressing it with bzip2 allows me to import it completely. So the problem must be the bzip2 export. I haven't had a chance to try the CompressOnFly setting yet.


  • Original author: noodlesnz

@pma-import
Copy link
Author

  • summary: Import doesn't process bzip2 completely --> Bzip2 export cannot be directly imported

  • Original author: lem9

@pma-import
Copy link
Author

Bzip2 export feature was withdrawn, see 144e00e.


  • Original author: lem9

@pma-import
Copy link
Author

  • summary: Bzip2 export cannot be directly imported --> (ok 4.1.5) Bzip2 export cannot be directly imported
  • status: open --> resolved
  • Priority: 5 --> 1

  • Original author: lem9

@pma-import
Copy link
Author

  • Status: resolved --> fixed

  • Original author: lem9

@pma-import pma-import added the Bug A problem or regression with an existing feature label Jul 24, 2015
@pma-import pma-import added this to the 4.1.5 milestone Jul 24, 2015
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug A problem or regression with an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants