Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>1) There is the concept of interceptors: <a href="http://msdn.microsoft.com/en-us/library/dd744842.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/dd744842.aspx</a></p> <p>But I think they won't satisfy you in your case: With change interceptors you can handle requests which try to change a specific entity. This could help you to avoid users without certain privileges to add/change/delete contact entities. With QueryInterceptors you can handle GET-Requests. But they don't allow you to restrict certain properties of your contact entity.</p> <p>You are not the first with such requirements -> <a href="https://stackoverflow.com/questions/7377119/wcf-dataservice-modify-object-before-returning-results/7377758#7377758">WCF Dataservice - modify object before returning results?</a></p> <p>Maybe you could use a combination of a (custom) ServiceOperation and a View to handle this.</p> <p>2) Yes, you can do this for instance by handling the ProcessingRequest-Event:</p> <pre><code>public class YourService : DataService&lt;Entities&gt; { /// &lt;summary&gt; /// The logger. /// &lt;/summary&gt; private readonly LogWriter logger; /// &lt;summary&gt; /// Initializes a new instance of the &lt;see cref="YourService"/&gt; class. /// &lt;/summary&gt; public YourService() { this.logger = EnterpriseLibraryContainer.Current.GetInstance&lt;LogWriter&gt;(); this.ProcessingPipeline.ProcessingRequest += this.ProcessingPipelineProcessingRequest; } /// &lt;summary&gt; /// OnProcessingRequest /// &lt;/summary&gt; /// &lt;param name="sender"&gt;source&lt;/param&gt; /// &lt;param name="e"&gt;event args&lt;/param&gt; public void ProcessingPipelineProcessingRequest(object sender, DataServiceProcessingPipelineEventArgs e) { this.logger.Write(new LogEntry { Message = "SOP ProcessingPipelineProcessingRequest: Unauthorized Access", Severity = TraceEventType.Warning }) } } </code></pre> <p>You can find all those ProcessingPipeline-Events here: <a href="http://msdn.microsoft.com/en-us/library/system.data.services.dataserviceprocessingpipeline(v=vs.103).aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/system.data.services.dataserviceprocessingpipeline(v=vs.103).aspx</a></p>
    singulars
    1. This table or related slice is empty.
    1. POWCF Data Service - Restrict visibility and logging queries
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USStefan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks. I've been using QueryInterceptors for filtering records and that works well but like you said, it's useless for filtering out properties. Wht do you mean by 'using a combination of a ServiceOperation and a View' ? I'll look into the ProcessingRequest event.
      singulars
      1. PO
      1. USSam
    2. COAlso, I have come across this article. I think it's a good compromise. I could have a 'full entity ' exposed to super users and a 'light' entity exposed to everyone. What do you think ?http://weblogs.asp.net/rajbk/archive/2010/05/15/pre-filtering-and-shaping-odata-feeds-using-wcf-data-services-and-the-entity-framework-part-2.aspx
      singulars
      1. PO
      1. USSam
    3. COHi! I meant that you can use a view for the user with less privileges. I don't know if you need that but the problem that occurs is that you can't insert any entites by using a view. That's why you could use a service operation in order to create the entity on the server side by using all the properties of the view as a parameter. Actually this may not the best or "prettiest" approach, but I personally disagree in having 1:1 relationships on the database only because WCF Data Services suck in terms of this requirement.
      singulars
      1. PO
      1. USStefan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload