@Fabio What I said to @Jose was not that entire model has to be read only, but just the part that lives in the translations table.
The things that live in primary table are going to be read and written. The things that live in translations table are going to be read only. Or more precisely there is going to be a different model for them that maps one to one with the table so it's not going to be a problem to work with them. So for this scenario I want to squash them to just few properties (so that they behave like a component) and I want to have a different model mapping to the translation table elsewhere which will fully expose what is in it. Hope that makes it clearer. On Mar 29, 6:15 am, José F. Romaniello <[email protected]> wrote: > 2011/3/28 Fabio Maulo <[email protected]> > > > Somebody said that you need a read-only model, > > I said so :( ... maybe i missunderstand he. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
