QinisoM
Forum Replies Created
Viewing 4 replies - 1 through 4 (of 4 total)
-
Hi Jeremy,
Thank you for for your response, I will action the above.
Kind regards,
Qiniso
Hi Anca, and thank you for the speedy response.
I would also like to point out that the non-paginated version of the above query
SELECT
tt.id, CASE WHEN ot.original is NULL THEN tt.original ELSE NULL END as tt_original,
tt.translated,
tt.domain AS tt_domain,
tt.plural_form,
tt.original_id AS tt_original_id,
ot.original,
ot.domain,
ot.context
FROM wp_trp_gettext_en_us AS tt
LEFT JOIN wp_trp_gettext_original_strings AS ot ON tt.original_id = ot.idcan return a very large results set, I would suggest that this be removed and only the paginated version is used.
Kind regards.
- This reply was modified 1 month, 2 weeks ago by QinisoM.
Hello,
Thanks for the prompt response. One last qustion:
Is there any feature planned in the near to add the DB operations as commands?
Kind regards.
Just an update, I found one a potential issue, the query is running repetively against the DB:
SELECT
tt.id,
CASE WHEN ot.original is NULL THEN tt.original ELSE NULL END as tt_original,
tt.translated,
tt.domain AS tt_domain,
tt.plural_form,
tt.original_id AS tt_original_id,
ot.original,
ot.domain, ot.context
FROMwp_trp_gettext_en_AS tt
LEFT JOINwp_trp_gettext_original_stringsAS ot ON tt.original_id = ot.idAdditionally it returns a very large result set without pagination, also because of no caching it runs repetitvely which causes the DB to slow down.
Viewing 4 replies - 1 through 4 (of 4 total)