> I'm not sure this is a great approach to in-database translations: you > have one function per string, which is cumbersome, bloated and probably > slow. I would suggest having a function that takes a string and returns > its translation, which is obtained from a couple of tables: one where > the original strings are stored and another which stores the > translations for each string into each language.
Perhaps like so https://www.gnumed.de/documentation/schema/release/#i18n.table.curr-lang SQL to be found here https://github.com/ncqgm/gnumed/tree/master/gnumed/gnumed/server/sql Karsten
