That's ok, I've been mixing up my left and my right today as well...
Actually, what about storing the original language in the nodes table, and just the translations in the nodes_t table. Then perhaps the following would be more efficient:
select nodes.id
, nodes.path
...
Hi r937,
Thanks for the (amazingly!) quick response. I was thinking somebody might respond in 24 hours if I was lucky :-)
I've never seen the coalesce function before - looks quite useful. In plain English, you are suggesting creating a third table to store the src/original translation?
If...
Hi,
Looking for a guru to help solve a tricky problem... I am storing objects in one table, and their translations in another with something like the following schema:
CREATE TABLE nodes (
id INTEGER NOT NULL PRIMARY KEY,
path VARCHAR(255) NOT NULL UNIQUE...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.