-
1. Re: Can I ignore some of the column when defining the view models?
shawkins Nov 12, 2010 10:06 AM (in response to jalen)Hi Jalen,
You should choose an appropriate literal as a default, such as null - "select c1 as cc1, null as cc2 ..."
Steve
-
2. Re: Can I ignore some of the column when defining the view models?
jalen Nov 12, 2010 11:09 AM (in response to shawkins)Thank you, Steven. But it is a little unconvenient when defining the transformation in development phase, especially there are many columns in one model.
-
3. Re: Can I ignore some of the column when defining the view models?
donald.ng Nov 17, 2010 9:19 PM (in response to jalen) -
4. Re: Can I ignore some of the column when defining the view models?
jalen Nov 18, 2010 5:13 AM (in response to donald.ng)Hello Donald,
We want our client still can see the column in the model but cannot retrieve the value.
-
5. Re: Can I ignore some of the column when defining the view models?
rareddy Nov 18, 2010 11:30 AM (in response to jalen)If you want restrict the users from accessing the data, why not look into data roles? The idea here is, you design the table with columns and their respective transformations to return the data. Then you define permissions on the table as to who is eligible to access the data.
Ramesh..
-
6. Re: Can I ignore some of the column when defining the view models?
jalen Nov 19, 2010 1:13 AM (in response to rareddy)Actually, we do not want to restrict users from accessing the data.
Since we are in development phase, many relationship has not been determined. So it would be convenient if we can leave some columns null. Especially if there are many uncertain or unneeded columns.
-
7. Re: Can I ignore some of the column when defining the view models?
rareddy Nov 19, 2010 9:58 AM (in response to jalen)So what you want is provide your uses with the metadata about the models but not the actual data. Actually you do not need to know "role" information for all the data roles stuff. There is new feature called "any-authenticated", where you can define default rules for any user who is logged in, then later you can fine tune who has the access.
If that does not work, then I am sorry, in that case as far I know there are no other options. This particular case specific to your use case and timing of your project phase you are in and does not fit in with general design model of Teiid, so we can not help with new feature request. What SteveH suggested above is the only solution.