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

Introduce logs database and migrate existing logs #6238

Closed
pippinsplugins opened this Issue Dec 18, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@pippinsplugins
Member

pippinsplugins commented Dec 18, 2017

Our current logs (sales, file downloads, api and requests) are stored as a post type of edd_log in the wp_posts table. This has had a number of negative consequences and it is time we move them to a sane storage location.

Related:

@pippinsplugins pippinsplugins added this to the 3.0 milestone Dec 18, 2017

@DrewAPicture DrewAPicture added this to Schema Changes in Release 3.0 Sprint Jan 4, 2018

@sunnyratilal

This comment has been minimized.

Show comment
Hide comment
@sunnyratilal

sunnyratilal Jan 4, 2018

Member

Just realised that is a duplicate of #3841. I'll close this issue as I've already started committing on the issue/3841 branch.

Member

sunnyratilal commented Jan 4, 2018

Just realised that is a duplicate of #3841. I'll close this issue as I've already started committing on the issue/3841 branch.

Release 3.0 Sprint automation moved this from Schema Changes to Done Jan 4, 2018

@sunnyratilal sunnyratilal removed this from Done in Release 3.0 Sprint Jan 4, 2018

@sunnyratilal sunnyratilal added Duplicate and removed Enhancement labels Jan 4, 2018

@sunnyratilal sunnyratilal removed this from the 3.0 milestone Jan 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment