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

Dealing with big Databases #48

Open
derpixler opened this issue Feb 18, 2016 · 2 comments
Open

Dealing with big Databases #48

derpixler opened this issue Feb 18, 2016 · 2 comments

Comments

@derpixler
Copy link
Contributor

If user has big Databases, the plugin cannot handle this. A solution can be that we call every table with a ajax. So we get a better performance and a working status.

Another issue is that I couldn't back up my database. It seems it was too big and I had timeouts and errors. What do you think about adding an option to backup just one table in the DB?
https://wordpress.org/support/topic/php-errors-69#post-8044179

@derpixler derpixler added this to the 3.1 milestone Feb 18, 2016
@derpixler
Copy link
Contributor Author

For a compromise solution see here 6e1f16d#commitcomment-16943919

derpixler added a commit that referenced this issue Apr 5, 2016
derpixler added a commit that referenced this issue Apr 5, 2016
@derpixler derpixler modified the milestones: 3.1, 3.2 Apr 6, 2016
@devbanana
Copy link
Contributor

@derpixler is this still an issue, or has it been resolved?

@bueltge bueltge removed this from the 3.2.0 milestone Nov 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants