Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If those two options are the two I am presented with, I would personally probably choose the interface way, simply because I think it looks cleaner. But this is entirely based on personal taste - I don't know enough about the inner workings of .NET to say for sure, but I don't know any case where the actual functionality of the two approaches would differ.</p> <p><strong>On the other hand</strong>, a much better approach would be to use Data Transfer Objects (DTO's) for sending data back and forth, and have the validation requirements on them. That is, instead of requiring that the <code>Movie</code> object meet all the validation requirements, you require that a <code>MovieInput</code> object meets all those requirements, and then create code to map a correct <code>MovieInput</code> into a <code>Movie</code>. (If you don't want to do that manually, you could use <a href="http://www.codeplex.com/automapper" rel="nofollow noreferrer">AutoMapper</a> or some other utility).</p> <p>The concept is basically to have something like a View Model object on the way <em>in</em> just as well as on the way <em>out</em> - I could just as well have let <code>MovieInput</code> be called <code>MovieViewModel</code> and use it for transferring of data both in and out of the server.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhen using Data Annotations with MVC, Pro and Cons of using an interface vs. a MetadataType
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTomas Lycken
    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. COSo if you had a facade between the UI and "persistence" layer, and you solely doled out these DTOs to the views, where do you put and integrate the more complex validation (business rules)? Implement `IValidateableObject` in the DTOs? That seems wrong... because all in all, we want to tie it all back to the UI using the integration points MVC provides (and dataannotations and ivalidateableobject could be used outside MVC too).
      singulars
      1. PO
      1. USkamranicus
    2. CO@subkamran: I see two possible scenarios here. 1) You need exactly the same input regardless of UI. In this case, the UI layer should be required to instantiate a common DTO, where the validation rules can be enforced, and the DTO can be used regardless of UI layer. 2) Input will be different in different UI layers to produce the same type of object in the business layer. In this case, you'll need UI specific DTO's, but the validation rules can still be enforced on the DTO - since the input requirements are different, the validation rules are as well. So you can always validate on your DTO's.
      singulars
      1. PO
      1. USTomas Lycken
    3. COI understand your logic and it makes sense, but won't I lose, say, all the Javascript integration? Because more often than not, my views deal with a subset of the object's properties (a DTO) but also with unrelated properties solely for the view (say a look up dictionary for select lists). So I can't really accept those as inputs from my service because they have needless properties I don't care about. Possibly, I could inherit from these DTOs, and create ViewModels off of them for MVC view consumption. That just creates more objects floating around but maybe that's fine?
      singulars
      1. PO
      1. USkamranicus
 

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