Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
espresso_table | Event Espresso - Staging Server

Support

Home › Forums › Custom Files › espresso_table

espresso_table

Posted: November 25, 2013 at 8:33 am

Viewing 1 reply thread


James Simon

November 25, 2013 at 8:33 am

I have modified espresso table so that it returns the data and takes users to an alternative registration page. However, I need to be able to modify the SQL so it only returns DISTINCT class names. Anotherwards if I have a class where it is running for 20 different dates I only want it to be returned once. The reason is the alternative registration page will show all the dates that they can pick from.

Does anyone know how to modify the SQL so it returns DISTINCT events based on name of class?


James Simon

November 25, 2013 at 9:46 am

Figured it out. For anyone interested I guess you don’t use DISTINCT in mysql it is GROUP BY.

SELECT e . *
FROM wp_events_detail e
WHERE e.is_active = ‘Y’
AND e.start_date >= ‘2013-11-25’
AND e.event_status != ‘S’
AND e.event_status != ‘D’
GROUP BY (
e.event_name
)
Viewing 1 reply thread

The support post ‘espresso_table’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Status: closed

Updated by James Simon 11 years, 3 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server