You can use a where clause when selecting from a veiew, so the following
should work for you:
CREATE VIEW my_view AS SELECT o.*, n.descr, n.lang
FROM nation n, org o
WHERE o.nation = n.code
SELECT * FROM my_view WHERE n.lang = someKnownQuantity
Michael Fork - CCNA - MCP -
On Fri, Mar 23, 2001 at 09:29:17AM -, Michael Ansley wrote:
> I think that the standard way to do this is to use a resource identifier,
> and then have a separate table with all strings. That's the way that most
> internationalisation is done in programs, and it's probably not bad for
> datab
Title: RE: [GENERAL] internationalizing text
I think that the standard way to do this is to use a resource identifier, and then have a separate table with all strings. That's the way that most internationalisation is done in programs, and it's probably not bad for databases either.
so who's got a clever implementation of cross-linguistic texts?
create table something (
id serial,
yadayada int4,
whatever date,
mumble float8,
en varchar(50), -- english
es varchar(50), -- e
