AW: [Mapbender-dev] i18n - table translations

[Heuser, Bjoern]

Hi Astrid,

I prefer using the trs_id column.
Because this column is also the primary key and the values are generated by a sequence I would wonder if there are double entries.

wkr

Björn

-----Ursprüngliche Nachricht-----
Von: mapbender_dev-bounces at lists.osgeo.org [mailto:mapbender_dev-bounces at lists.osgeo.org] Im Auftrag von Astrid Emde (WhereGroup)
Gesendet: Montag, 13. August 2007 09:40
An: Mapbender_dev
Betreff: [Mapbender-dev] i18n - table translations

Hi devs, hi peter, hi christoph,

 I have a question about the new table translation.

 At the moment the table looks like this:

CREATE TABLE public.translations
(
  trs_id int4 NOT NULL DEFAULT nextval('translations_trs_id_seq'::regclass),
  locale varchar(8),
  msgid varchar(512),
  msgstr varchar(512),
  CONSTRAINT translations_pkey PRIMARY KEY (trs_id)
);

Do we need the column trs_id ? Or can we skip it? It would we easier 
without the column, as we won't get problems with double entries in the 
trs_id column.

What do you think?

Best regards astrid
_______________________________________________
Mapbender_dev mailing list
Mapbender_dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapbender_dev