Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In terms of best practice / a more elegant way to do this, you should look at creating a Recipe case class to hold all the info for your recipe; this will make your code a little cleaner and easier to work with:</p> <pre><code>case class Recipe(val id: Long, val cuisine: String, val instructions: String, val quantity: Int, val units: String, val brand: String, val name: String) </code></pre> <p>Note: all the fields are explicitly labeled as vals for ease of use when I access the fields in the view. You can then transform your queries into an object (from <a href="https://stackoverflow.com/questions/13097492/scala-slick-query-return-value">scala slick query return value</a>)</p> <pre><code>def getRecipe(recID: Long): Option[Recipe] = { val q = for { r &lt;- Recipes if r.id === recID ri &lt;- RecipeIngredient if ri.recID === recID i &lt;-Ingredients if i.id === ri.ingID } yield (r.id, r.cuisine, r.instructions, ri.quantity, ri.units, i.brand, i.name) q.firstOption map { case (id, cui, ins, qua, uni, bra, na) =&gt; Recipe(id, cui, ins, qua, uni, bra, na) } } </code></pre> <p>You can then pass this to your view: </p> <pre><code>@(message: String, recipe: Recipe) @main("Site name") { @recipe match { case r:Some(Recipe) =&gt; { &lt;h2&gt;--Recipe--&lt;/h2&gt; RecID: @r.id &lt;br&gt; Cuisine: @r.cuisine &lt;br&gt; Instructions: @r.instructions &lt;br&gt; &lt;h2&gt;--Ingredients--&lt;/h2&gt; Ingredient: @r.quantity @r.units of @r.brand @r.name&lt;br&gt; } case None =&gt; { &lt;h2&gt;No Recipe&lt;/h2&gt; } } } </code></pre> <p>You can do some different things, like make a companion object class for the Recipe case class, get rid of the Option[Recipe] being passed to your view, etc. This will also make it easier should you want to select multiple recipes and pass them in a List[Recipe] to a view which you could then iterate over.</p> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POPlay Framework Templates - Iterating over a list issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. UStcsullens
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPlay Framework Templates - Iterating over a list issue
      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. VTAcceptedByOriginator
    1. COThanks for your help - this certainly looks more elegant so I'll give it a try. Is it possible to modify it so that each Recipe can have multiple Ingredients? Based on the code above, it looks like the Recipe case class will only hold one ingredient?
      singulars
      1. PO
      1. USdbau
    2. COYes you can do that, just change the ingredients field in the Recipe; you could just have a List of tuples of ingredient info: List((name: String, quantity: Int, brand: String)) kind of thing, but even better you could add a layer of abstraction and create an Ingredient class with appropriate fields. Basically you want to link your database schema with objects that match the information you're trying to store. So when you add / remove / get information from the database, your doing it via slick's / anorm's ability to construct objects from queries. I apologize if this is not exactly clear
      singulars
      1. PO
      1. UStcsullens
    3. COThanks for your help tc - as you can tell I'm quite new to Scala! I managed to use case classes and build a `findRecipe` function which returns a `RecipeWithIngredients` object that has a sub-list containing the ingredients associated with the recipe, but I feel that my code is far from elegant. Could you review this and let me know your thoughts? http://pastebin.com/kt3ruLUY Thanks!
      singulars
      1. PO
      1. USdbau
 

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