Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think the fault lies in the purity requirement. Design patterns, MVVM included, are a tool in the toolbox, not an end unto themselves. If it makes more sense to break with the purity of the model for a well-considered case (and it clearly looks like you've considered this case), then break with the model.</p> <p>If that works for you, and you don't believe it's an undue maintenance burden, then I'd say that nothing is wrong with what you've done. I think that you've clearly met the burden of proof for showing that this is a reasonable solution to your problem in spite of what a pure MVVM implementation might be.</p> <p>(I consider this argument similar to the arguments for multiparadigm languages. While a Pure OO approach can be applied, sometimes doing things in a more functional way is more appropriate. While a Pure Functional approach can be applied, sometimes the trade offs show that OO techniques are more than worth the while.)</p>
    singulars
    1. This table or related slice is empty.
    1. POMVVM Madness: Commands
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGreg D
    1. USGreg D
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMVVM Madness: Commands
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAgreed, excessive purity, whether with MVVM or any other pattern, becomes counterproductive. I've seen people saying that you shouldn't even use value converters because your view model should be doing all the work -- a surefire recipe for tight coupling and architectural fail. MVVM is a (very) useful guiding principle to *how to think* in WPF so as to make your code simple and decoupled. It should never become a stick with which to beat your code into an unnatural mess of twisted complexity.
      singulars
      1. PO
      1. USitowlson
    2. COThe original question mirrors my own frustrations trying to do pure MVVM and I like your answer, however I'd like to point out that when learning a new pattern, particularly one as othello-like as MVVM (easy to learn, difficult to master), the best way to approach that learning is to do everything you can to force yourself into pattern purity. Only after you've learned the hard lessons can you gain the experience necessary to know when and how to break the pattern.
      singulars
      1. PO
      1. USRandolpho
    3. CO@Randolpho: You make a very good and cogent point, and I completely agree. I strive for purity of my understanding of the pattern in most of my personal projects, and certainly the small ones. I think MVVM in particular is tricky because there's so much gray area wrt what belongs in the view vs the view model. My personal opinion is that anything that doesn't affect application state stays out of the VM and in the view (maybe even the codebehind!), but am I then writing something more like an MVP? Dunno. Very subtle stuff!
      singulars
      1. PO
      1. USGreg D
 

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