Hi everybody,

I've got a quite annoying problem with my collegues' database structure.
I've tried to solve this over and over again for half a year by now.

We have all kinds of entities with translatable properties, e.g. a Catalog with a translatable title.

That wouldn't be much of a problem, but the corresponding db-structure
is a column for every language, like:
ID | TITLE | TITLE_E | TITLE_D | TITLE_FR | etc...

Well, the database is generated during deployment depending on the configured languages.
Thus I don't know (at build-time) how many columns have to be read/written so I can't supply them in my UserType-Mapping.

Further I don't have access to our deployment tool, thus I can't generate the mapping at deployment.

Any Idea, how to implement a UserType with 'dynamically' calculated columns?
Or any other Idea, how to get the described DB-Structure (titles) into a Map-like object?

Thnx for any suggestions. ;)

P.S. Please excuse my bumpy english... I'm not a native speaker... ;)

Hi !!

I think the idea to create one column by language is the bad idea.
In general, when you modelise database, you must have a fixed model.

For your problem,
you can create three table

With the modelisation, the model is fixed and can manage severals language.

++

Hi fedfil,

first of all: Thanks for you reply ;-)

Well, the problem is, that I'm stuck with that miserable DB model.
I'm not allowed to change that.

My colleagues are hacking low-level JDBC where this model is not really
a problem... The simply type "SELECT TITLE_" + language + " FROM someTable...", execute that and get the results from the ResultSet.

But they do it over and over and over again, for every bean, for every usecase, which IMHO is VERY errorprone and VERY VERY annoying.

I'd like to use Hibernate instead, but due to that F***ING DB model I've not been able to do so.

Time is running short, and I'm far from beeing finished... ;(

So I tried (for the first time of my life) to get the help I need from a forum.

so far,
Greez Windi ;)