Databases
StackOverflow2013
Postsdbo
POData grouping in SQL
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POData grouping in SQL
    primarykey
    data
    text
    <p>I am working on a small project using C# and EF5.0 and I need to group some data. Let say I have table of columns in a building like shown below.</p> <pre><code>+----------+--------Columns Table--+------+------+ | ColumnID |ColumnName|Width|Length|Height|number| +----------+----------+-----+------+------+------+ | 1 | C101 | 50 | 70 | 250 | 1 | | 2 | C102 | 70 | 70 | 250 | 1 | | 3 | C103 | 70 | 60 | 250 | 1 | | 4 | C104 | 90 | 70 | 250 | 1 | | 5 | C105 | 40 | 50 | 250 | 1 | | 6 | C106 | 50 | 70 | 250 | 1 | | 7 | C107 | 50 | 60 | 250 | 1 | | 8 | C108 | 70 | 70 | 250 | 1 | +----------+----------+-----+------+------+------+ </code></pre> <p>I need a C# code to see the above data groupped like this:</p> <pre><code>+----------+---Groupped Columns Table-----+------+ |G_ColumnID|ColumnName|Width|Length|Height|number| +----------+----------+-----+------+------+------+ | 1 |C(101-106)| 50 | 70 | 250 | 2 | | 2 |C(102-108)| 70 | 70 | 250 | 2 | | 3 | C103 | 70 | 60 | 250 | 1 | | 4 | C104 | 90 | 70 | 250 | 1 | | 5 | C105 | 40 | 50 | 250 | 1 | | 6 | C107 | 50 | 60 | 250 | 1 | +----------+----------+-----+------+------+------+ </code></pre> <p>I prefer clues than the exact solution.</p> <p><strong>EDIT :</strong> Below code shows my current state. I think I can find the columns with the same Height, Width and Length using this code. But I am not sure how to generate a new name for the group.</p> <pre><code>using (pehlivanEntities context = new pehlivanEntities()) { foreach (var item in context.table1) { int id = item.ColumnID; foreach (var item2 in context.table1) { int id2 = item2.ColumnID; if (id != id2) { if (item.Width == item2.Width) { if (item.Length == item2.Length) { if (item.Height == item2.Height) { //Alter item.ColumnName //increase item.number by one //Remove item2 } } } } } } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USHasan
    1. USHasan
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POData grouping in SQL
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POData grouping in SQL
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POData grouping in SQL
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for "I prefer clues than the exact solution"
      singulars
      1. POData grouping in SQL
      1. USspender
    2. COPurely a nitpick, but you may want to have `C(101,106)` instead of `C(101-106)`. With the first, to me that indicates columns 101 and 106, whereas using the dash indicates columns 101 through 106, which confused me at first.
      singulars
      1. POData grouping in SQL
      1. USLittleBobbyTables
    3. COJust to clarify, it looks like you're grouping on rows that have the same `Width`, `Length`, and `Height` values, correct? Right off the top of my head, it seems like getting a `ColumnName` result like you want in your grouping will be tough, since you wouldn't be grouping on the `ColumnName`. Would probably have to do a `GroupBy`, then add the `ColumnName` stuff after.
      singulars
      1. POData grouping in SQL
      1. USGromer
 

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