Hi,

when we started, we had two distinct tables, but this solution was too
slow, as we have a few hundred thousand texts. So we put our texts in
one table. This improved the performance significantly.

Wouldn't be a mechanism to allow people to provide their own storage
classes be of general interest? Or am I the only one with such
unorthodox constructs?
With such a mechanism, one could also store/retrieve data from ldap or
plain files etc.

Regards

Claus



Am Mo, 2003-12-08 um 12.45 schrieb Antonio Gallardo:
> Claus Radloff dijo:
> > Hi,
> >
> > for some cases this could be a solution. But the majority needs the
> > texts in all available languages, so the user can edit the description
> > in these languages at once.
> 
> OK. I understand. For similars cases we builded a BeanList. And just
> search by the first value, living the language free.
> 
> A two tables can be your solution:
> 
> class TextType
> {
>   Integer id;
>   String type;
>   String name;
> }
> 
> class Text
> {
>   Integer id;
>   Integer language;
>   Map text;
> }
> 
> In the O/R mapping, in TextType define a collection for Text. This would
> work fine. We do the same for User and Permissions, where 1 user can have
> many permisions.
> 
> Is this OK? :-D
> 
> Best Regards,
> 
> Antonio Gallardo



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to