Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I just ran a test that works fine: </p> <pre><code>var sql = "select cast(1 as decimal) ProductId, 'a' ProductName, 'x' AccountOpened, cast(1 as decimal) CustomerId, 'name' CustomerName"; var item = connection.Query&lt;ProductItem, Customer, ProductItem&gt;(sql, (p, c) =&gt; { p.Customer = c; return p; }, splitOn: "CustomerId").First(); item.Customer.CustomerId.IsEqualTo(1); </code></pre> <p>The splitOn param needs to be specified as the split point, it defaults to Id. If there are multiple split points, you will need to add them in a comma delimited list.</p> <p>Say your recordset looks like this: </p> <pre> ProductID | ProductName | AccountOpened | CustomerId | CustomerName --------------------------------------- ------------------------- </pre> <p>Dapper needs to know how to split the columns in this order into 2 objects. A cursory look shows that the Customer starts at the column <code>CustomerId</code>, hence <code>splitOn: CustomerId</code>.</p> <p>There is a <strong>big</strong> caveat here, if the column ordering in the underlying table is flipped for some reason:</p> <pre> ProductID | ProductName | AccountOpened | CustomerName | CustomerId --------------------------------------- ------------------------- </pre> <p><code>splitOn: CustomerId</code> will result in a null customer name. </p> <p>If you specify <code>CustomerId,CustomerName</code> as split points, dapper assumes you are trying to split up the result set into 3 objects. First starts at the beginning, second starts at <code>CustomerId</code>, third at <code>CustomerName</code>. </p>
    singulars
    1. This table or related slice is empty.
    1. POCorrect use of Multimapping in Dapper
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSam Saffron
    1. USSam Saffron
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCorrect use of Multimapping in Dapper
      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. VTAcceptedByOriginator
    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. COThanks Sam. Yeah your right it was the return order of the columns that was the issue with CustomerName | CustomerId being returned CustomerName was comming back null.
      singulars
      1. PO
      1. USRichard Forrest
    2. COOne thing to remember is you can't have spaces in the `spliton`, ie `CustomerId,CustomerName` not `CustomerId, CustomerName`, since Dapper doesn't `Trim` the results of the string split. It will just throw the generic spliton error. Drove me crazy one day.
      singulars
      1. PO
      1. USjes
 

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