Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Don's suggestion of blaze-html is one way to do it, but I find that when I do it that way I have more of a tendency to violate the commonly used MVC design pattern by embedding the view (in this case the HTML) into your Haskell code. In some cases if you're just trying to do something quick and dirty this may be the thing to do. But if you want this to fit into a larger application in a way that separates the view from the controller and allows designers to work with it who are unfamiliar with Haskell, then you might be better off using the Heist template system.</p> <p>We have a Heist tutorial <a href="http://snapframework.com/docs/tutorials/heist" rel="nofollow">here</a>. I also recently wrote a series of <a href="http://softwaresimply.blogspot.com/" rel="nofollow">blog posts</a> about just this sort of thing. The <a href="http://softwaresimply.blogspot.com/2011/04/views-controllers-and-heist.html" rel="nofollow">second post in the series</a> in particular is probably the most relevant to your question. Here's some code that does something like what you want:</p> <pre><code>names :: [(Text,Text)] names = [("Alice", "Anderson"), ("Bob", "Brown")] nameSplice :: (Text, Text) -&gt; Splice Application nameSplice name = runChildrenWithText [("firstName", fst name), ("lastName", snd name)] namesSplice :: Splice Application namesSplice = mapSplices nameSplice names </code></pre> <p>After you bind the names splice somewhere in your application with <code>bindSplice "names" namesSplice</code> you can get at this data from a template like this:</p> <pre><code>&lt;table&gt; &lt;names&gt; &lt;tr&gt;&lt;td&gt;&lt;firstName/&gt;&lt;/td&gt;&lt;td&gt;&lt;lastName/&gt;&lt;/td&gt;&lt;/tr&gt; &lt;/names&gt; &lt;/table&gt; </code></pre> <p>The nice thing about this is that the web designer has complete control over how the names are displayed. If they needed to change the display to say an unordered list in the format "lastname, firstname" that would be very easy to do here without needing to recompile your application.</p>
    singulars
    1. This table or related slice is empty.
    1. PORender haskell list data to web page
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmightybyte
    1. USmightybyte
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORender haskell list data to web page
      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. VTAcceptedByOriginator
    1. COThanxxxx,Yhaa This works very well!!!
      singulars
      1. PO
      1. US123Ex
    2. COI wouldn't say that blaze-html violates MVC as long as you keep the html-generation part separate from the IO/logic part, for example by having them in separate modules. In either case, there's going to have to be some kind of interface or convention between the controller and the view, and there are benefits to having this interface be automatically verifiable by a compiler.
      singulars
      1. PO
      1. UShammar
    3. CO@hammar Good point. It is possible to preserve MVC and still use the blaze approach. Although in my experience the run-time/compile-time separation that heist gives you does tend to make view/controller separation easier.
      singulars
      1. PO
      1. USmightybyte
 

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