|
Giant Dwarf
|
May 5, 2017 at 1:07 am
Hi there, quick question/request. Just poking around in the database to look at some post data and discovered to my horror that the wp_posts table had almost 20,000 entries. Nearly had a heart attack because I thought we must have had some bug in a plugin. Then I realised that a large number of these entries weren’t posts or events at all, but were mostly the post type ‘espresso_attendees’.
Two questions in relation to this. Firstly, how crucial are these to the functioning of EE? We’re not letting customers log in to the site, so long term most of these entires are doing nothing but weighing down the database. However I don’t want to just go back and delete old customer records as I don’t know if these entries are linked into events or other data that might break if they have relations to these entries and they’re not there anymore.
Second, is more a request for future dev. Could it possibly be looked into storing these records outside of post data? Seems like these entries are primarily made up of a creation date plus three strings for Name, Slug, and bio. However, because this is a post there’s 18 other un-nessecary cells stored with each customer. There’s also a heap of redundant data in storing the string ‘No Biography Provided’ twice for every attendee (as post content and excerpt), which could probably be more efficiently dealt with. It’s only a few bytes and a few extra cells but multiplied by 20,000 it really has an impact on the performance of querying things like posts and events when the database also has to dig through thousands of attendee records as well.
Thanks!
|
|
Josh
|
May 5, 2017 at 7:44 am
The attendee data is linked to your registrations and transaction records. So if you delete the attendee records, you will see errors when you load up past events registration and transaction records.
What I find interesting about your comments is Event Espresso has largely been criticized for not using the posts table and instead using custom tables. Here’s an example. If you want to discuss the merits of not using the posts table to store attendee data with the developers, you are invited to post an issue on Github:
https://github.com/eventespresso/event-espresso-core/issues
|
|
Giant Dwarf
|
May 12, 2017 at 12:55 am
Righto thanks, was afraid of that, guess we’ll just need to migrate onto a fresh install at some point. Unfortunately we never really have an appropriate time we can make a clean break with events, which seems to be the root of a few issues we’ve had with our database becoming unweildly.
And thanks for the link, didn’t realise there’d been a lot of debate over this, but I know how WordPress developers can get when a plugin deviates from the orthodoxy of one-table-to-rule-them all. Don’t envy you all there having to work through those discussions!
|
