Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. IEnumerable OrderBy on a text field

IEnumerable OrderBy on a text field

Scheduled Pinned Locked Moved C#
sysadminquestion
18 Posts 4 Posters 2 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M manognya kota

    Hi, try the below code snippet var newList = people.OrderBy(name => name.Name).ToList(); -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

    _ Offline
    _ Offline
    __John_
    wrote on last edited by
    #4

    Hi, thanks for looking at this. Not sure what I am doing wrong. I tried...

             DataContext = new DataClasses1DataContext();
    
             var people = from name in DataContext.Table\_Peoples
                          where name.IQ < 3
                          select name;
    
             var peopleOrdered = people.OrderBy(name => name.Name).ToList();
    

    'Name' is decared as follows...

    [global::System.Data.Linq.Mapping.ColumnAttribute(Storage="_Name", DbType="Text", UpdateCheck=UpdateCheck.Never)]
    public string Name
    {
    get
    {
    return this._Name;
    }
    set
    {
    if ((this._Name != value))
    {
    this._Name = value;
    }
    }
    }

    It is still thowing the same exception.

    _ 1 Reply Last reply
    0
    • _ __John_

      Hi, thanks for looking at this. Not sure what I am doing wrong. I tried...

               DataContext = new DataClasses1DataContext();
      
               var people = from name in DataContext.Table\_Peoples
                            where name.IQ < 3
                            select name;
      
               var peopleOrdered = people.OrderBy(name => name.Name).ToList();
      

      'Name' is decared as follows...

      [global::System.Data.Linq.Mapping.ColumnAttribute(Storage="_Name", DbType="Text", UpdateCheck=UpdateCheck.Never)]
      public string Name
      {
      get
      {
      return this._Name;
      }
      set
      {
      if ((this._Name != value))
      {
      this._Name = value;
      }
      }
      }

      It is still thowing the same exception.

      _ Offline
      _ Offline
      __John_
      wrote on last edited by
      #5

      Ok I got it to work like this...

                 DataContext = new DataClasses1DataContext();
      
                 var people = from name in DataContext.Table\_Peoples
                              where name.IQ < 3
                              select name;
      
                 List<Table\_People> listPeople = people.ToList();
      
                 var peopleOrdered = listPeople.OrderBy(name => name.Name).ToList();
      

      But I dont understand why I have to copy to a List first?

      M V 2 Replies Last reply
      0
      • _ __John_

        Ok I got it to work like this...

                   DataContext = new DataClasses1DataContext();
        
                   var people = from name in DataContext.Table\_Peoples
                                where name.IQ < 3
                                select name;
        
                   List<Table\_People> listPeople = people.ToList();
        
                   var peopleOrdered = listPeople.OrderBy(name => name.Name).ToList();
        

        But I dont understand why I have to copy to a List first?

        M Offline
        M Offline
        manognya kota
        wrote on last edited by
        #6

        Quote:

        __John_ wrote:

        List<Table_People> listPeople = people.ToList();   var peopleOrdered = listPeople.OrderBy(name => name.Name).ToList();

        To order the list, it requires the set of names to be in a format and we are storing it as the enumerable list.

        -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

        _ 1 Reply Last reply
        0
        • M manognya kota

          Quote:

          __John_ wrote:

          List<Table_People> listPeople = people.ToList();   var peopleOrdered = listPeople.OrderBy(name => name.Name).ToList();

          To order the list, it requires the set of names to be in a format and we are storing it as the enumerable list.

          -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

          _ Offline
          _ Offline
          __John_
          wrote on last edited by
          #7

          Hi Manognya, I dont understand why List.OrderBy works when IEnumerable.OrderBy does not? I am not sure what you mean when you say 'in a format'? Thanks.

          M 2 Replies Last reply
          0
          • _ __John_

            Hi Manognya, I dont understand why List.OrderBy works when IEnumerable.OrderBy does not? I am not sure what you mean when you say 'in a format'? Thanks.

            M Offline
            M Offline
            manognya kota
            wrote on last edited by
            #8

            Hi John, The syntax of OrderBy is:

            Public Shared Function OrderBy(Of TSource, TKey) ( _
            source As IEnumerable(Of TSource), _
            keySelector As Func(Of TSource, TKey) _
            ) As IOrderedEnumerable(Of TSource)

            Parameters

            source
            Type: System.Collections.Generic.IEnumerable(Of TSource)
            A sequence of values to order.

            keySelector
            Type: System.Func(Of TSource, TKey)
            A function to extract a key from an element.

            we need to convert the source to be of type

            System.Collections.Generic.IEnumerable

            Hope this helps.

            -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

            1 Reply Last reply
            0
            • _ __John_

              Hi Manognya, I dont understand why List.OrderBy works when IEnumerable.OrderBy does not? I am not sure what you mean when you say 'in a format'? Thanks.

              M Offline
              M Offline
              manognya kota
              wrote on last edited by
              #9

              Also, look at the link http://msdn.microsoft.com/en-us/library/bb534966.aspx#Y1297[^] Do not forget to vote the answer that serves the purpose ;)

              -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

              _ 1 Reply Last reply
              0
              • M manognya kota

                Also, look at the link http://msdn.microsoft.com/en-us/library/bb534966.aspx#Y1297[^] Do not forget to vote the answer that serves the purpose ;)

                -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

                _ Offline
                _ Offline
                __John_
                wrote on last edited by
                #10

                Thanks, it is slowly becoming clear, I probably just need to think about it a bit more. I do sometimes find templates a bit confusing. +5

                M 1 Reply Last reply
                0
                • _ __John_

                  Thanks, it is slowly becoming clear, I probably just need to think about it a bit more. I do sometimes find templates a bit confusing. +5

                  M Offline
                  M Offline
                  manognya kota
                  wrote on last edited by
                  #11

                  Agree..templates is always little tricky(for me either ;))...But, Once got..makes life easy:)

                  -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

                  1 Reply Last reply
                  0
                  • _ __John_

                    Ok I got it to work like this...

                               DataContext = new DataClasses1DataContext();
                    
                               var people = from name in DataContext.Table\_Peoples
                                            where name.IQ < 3
                                            select name;
                    
                               List<Table\_People> listPeople = people.ToList();
                    
                               var peopleOrdered = listPeople.OrderBy(name => name.Name).ToList();
                    

                    But I dont understand why I have to copy to a List first?

                    V Offline
                    V Offline
                    Vincent Blais
                    wrote on last edited by
                    #12

                    The difference is not the IEnumerable or the List but where the OrderBy take place. When you call ToList,or any greedy query operators, you execute your Ling query against your DB. After that, all Linq operation are executed in memory and Linq-to-object can do more things in than Linq-to-sql, or Linq-to-entities

                    Vince Remember the dead, fight for the living

                    _ 1 Reply Last reply
                    0
                    • V Vincent Blais

                      The difference is not the IEnumerable or the List but where the OrderBy take place. When you call ToList,or any greedy query operators, you execute your Ling query against your DB. After that, all Linq operation are executed in memory and Linq-to-object can do more things in than Linq-to-sql, or Linq-to-entities

                      Vince Remember the dead, fight for the living

                      _ Offline
                      _ Offline
                      __John_
                      wrote on last edited by
                      #13

                      Thanks Vince, that explains it a bit more. I think i can now understand what the debuger is showing me. It uses a 'lazy' stratergy, ie. only evaluating an expression or executing a function when the result is actually needed, am I right? BTW: How can I enumerate the results more that once? Hoping that is not too stupid a question :doh: Thanks - John.

                      _ V 2 Replies Last reply
                      0
                      • _ __John_

                        Thanks Vince, that explains it a bit more. I think i can now understand what the debuger is showing me. It uses a 'lazy' stratergy, ie. only evaluating an expression or executing a function when the result is actually needed, am I right? BTW: How can I enumerate the results more that once? Hoping that is not too stupid a question :doh: Thanks - John.

                        _ Offline
                        _ Offline
                        __John_
                        wrote on last edited by
                        #14

                        http://msdn.microsoft.com/en-us/library/s793z9y2.aspx[^]

                        You cannot set Current to the first element of the collection again; you must create a new enumerator instance instead.

                        Seems a strange way of going about things but I am sure there is a reason :confused:

                        1 Reply Last reply
                        0
                        • _ __John_

                          Thanks Vince, that explains it a bit more. I think i can now understand what the debuger is showing me. It uses a 'lazy' stratergy, ie. only evaluating an expression or executing a function when the result is actually needed, am I right? BTW: How can I enumerate the results more that once? Hoping that is not too stupid a question :doh: Thanks - John.

                          V Offline
                          V Offline
                          Vincent Blais
                          wrote on last edited by
                          #15

                          __John_ wrote:

                          It uses a 'lazy' strategy, ie. only evaluating an expression or executing a function when the result is actually needed, am I right?

                          Yes you are right. It's a principle of Linq to defer execution until is needed. And Linq also evaluate only the elements needed to return the result Let's take Wayne List and do some examples

                          List peoples = new List {new Person("wayne"), new Person("sarah"), new Person("mark"), new Person("simon"), new Person("ashleigh"), new Person("dave"), new Person("connor"), new Person("bronwyn"), new Person("chantelle"), new Person("will"), new Person("chris")};

                          int Count = people.Count(p => p.Name.StartsWith("w")); //<-- Count is a greedy operator and all persons are evaluated for a result of 2.

                          var firstperson = people.Where(p => p.Name.Length == 5).Take(3);
                          foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Sarah, Mark and Simon will be evaluated. The rest of the list is left alone
                          {
                          Console.WriteLine(p.Name);
                          }

                          // And to show you when Linq expression are evaluated, try
                          var firstperson2 = people.Where(p => p.Name.Length == 5).Take(3);
                          people.Insert(1, new Person("Vince"));

                          foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Vince ans Sarah, will be evaluated. The rest of the list is left alone
                          {
                          Console.WriteLine(p.Name);
                          }

                          http://blogs.msdn.com/b/charlie/archive/2007/12/09/deferred-execution.aspx[^]

                          __John_ wrote:

                          BTW: How can I enumerate the results more that once?

                          If you use a Enumerator, you can use Reset to set the enumerator to its initial position, which is before the first element in the collection. But if you use a foreach loop, you can reuse an Enumerable many times. The foreach loop will start at the beginning every time.

                          Vince Remember the dead, fight for the living

                          _ W M 3 Replies Last reply
                          0
                          • V Vincent Blais

                            __John_ wrote:

                            It uses a 'lazy' strategy, ie. only evaluating an expression or executing a function when the result is actually needed, am I right?

                            Yes you are right. It's a principle of Linq to defer execution until is needed. And Linq also evaluate only the elements needed to return the result Let's take Wayne List and do some examples

                            List peoples = new List {new Person("wayne"), new Person("sarah"), new Person("mark"), new Person("simon"), new Person("ashleigh"), new Person("dave"), new Person("connor"), new Person("bronwyn"), new Person("chantelle"), new Person("will"), new Person("chris")};

                            int Count = people.Count(p => p.Name.StartsWith("w")); //<-- Count is a greedy operator and all persons are evaluated for a result of 2.

                            var firstperson = people.Where(p => p.Name.Length == 5).Take(3);
                            foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Sarah, Mark and Simon will be evaluated. The rest of the list is left alone
                            {
                            Console.WriteLine(p.Name);
                            }

                            // And to show you when Linq expression are evaluated, try
                            var firstperson2 = people.Where(p => p.Name.Length == 5).Take(3);
                            people.Insert(1, new Person("Vince"));

                            foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Vince ans Sarah, will be evaluated. The rest of the list is left alone
                            {
                            Console.WriteLine(p.Name);
                            }

                            http://blogs.msdn.com/b/charlie/archive/2007/12/09/deferred-execution.aspx[^]

                            __John_ wrote:

                            BTW: How can I enumerate the results more that once?

                            If you use a Enumerator, you can use Reset to set the enumerator to its initial position, which is before the first element in the collection. But if you use a foreach loop, you can reuse an Enumerable many times. The foreach loop will start at the beginning every time.

                            Vince Remember the dead, fight for the living

                            _ Offline
                            _ Offline
                            __John_
                            wrote on last edited by
                            #16

                            +5 Thanks Vince.

                            1 Reply Last reply
                            0
                            • V Vincent Blais

                              __John_ wrote:

                              It uses a 'lazy' strategy, ie. only evaluating an expression or executing a function when the result is actually needed, am I right?

                              Yes you are right. It's a principle of Linq to defer execution until is needed. And Linq also evaluate only the elements needed to return the result Let's take Wayne List and do some examples

                              List peoples = new List {new Person("wayne"), new Person("sarah"), new Person("mark"), new Person("simon"), new Person("ashleigh"), new Person("dave"), new Person("connor"), new Person("bronwyn"), new Person("chantelle"), new Person("will"), new Person("chris")};

                              int Count = people.Count(p => p.Name.StartsWith("w")); //<-- Count is a greedy operator and all persons are evaluated for a result of 2.

                              var firstperson = people.Where(p => p.Name.Length == 5).Take(3);
                              foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Sarah, Mark and Simon will be evaluated. The rest of the list is left alone
                              {
                              Console.WriteLine(p.Name);
                              }

                              // And to show you when Linq expression are evaluated, try
                              var firstperson2 = people.Where(p => p.Name.Length == 5).Take(3);
                              people.Insert(1, new Person("Vince"));

                              foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Vince ans Sarah, will be evaluated. The rest of the list is left alone
                              {
                              Console.WriteLine(p.Name);
                              }

                              http://blogs.msdn.com/b/charlie/archive/2007/12/09/deferred-execution.aspx[^]

                              __John_ wrote:

                              BTW: How can I enumerate the results more that once?

                              If you use a Enumerator, you can use Reset to set the enumerator to its initial position, which is before the first element in the collection. But if you use a foreach loop, you can reuse an Enumerable many times. The foreach loop will start at the beginning every time.

                              Vince Remember the dead, fight for the living

                              W Offline
                              W Offline
                              Wayne Gaylard
                              wrote on last edited by
                              #17

                              Nice examples - thanks!

                              When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman

                              1 Reply Last reply
                              0
                              • V Vincent Blais

                                __John_ wrote:

                                It uses a 'lazy' strategy, ie. only evaluating an expression or executing a function when the result is actually needed, am I right?

                                Yes you are right. It's a principle of Linq to defer execution until is needed. And Linq also evaluate only the elements needed to return the result Let's take Wayne List and do some examples

                                List peoples = new List {new Person("wayne"), new Person("sarah"), new Person("mark"), new Person("simon"), new Person("ashleigh"), new Person("dave"), new Person("connor"), new Person("bronwyn"), new Person("chantelle"), new Person("will"), new Person("chris")};

                                int Count = people.Count(p => p.Name.StartsWith("w")); //<-- Count is a greedy operator and all persons are evaluated for a result of 2.

                                var firstperson = people.Where(p => p.Name.Length == 5).Take(3);
                                foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Sarah, Mark and Simon will be evaluated. The rest of the list is left alone
                                {
                                Console.WriteLine(p.Name);
                                }

                                // And to show you when Linq expression are evaluated, try
                                var firstperson2 = people.Where(p => p.Name.Length == 5).Take(3);
                                people.Insert(1, new Person("Vince"));

                                foreach (var p in firstperson) // <-- evaluation start where and only Wayne, Vince ans Sarah, will be evaluated. The rest of the list is left alone
                                {
                                Console.WriteLine(p.Name);
                                }

                                http://blogs.msdn.com/b/charlie/archive/2007/12/09/deferred-execution.aspx[^]

                                __John_ wrote:

                                BTW: How can I enumerate the results more that once?

                                If you use a Enumerator, you can use Reset to set the enumerator to its initial position, which is before the first element in the collection. But if you use a foreach loop, you can reuse an Enumerable many times. The foreach loop will start at the beginning every time.

                                Vince Remember the dead, fight for the living

                                M Offline
                                M Offline
                                manognya kota
                                wrote on last edited by
                                #18

                                Nice examples.Thanks.Its more clear now.

                                -Manognya __________________________________________________ $ God gives what is best.Not what all you wish :)

                                1 Reply Last reply
                                0
                                Reply
                                • Reply as topic
                                Log in to reply
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes


                                • Login

                                • Don't have an account? Register

                                • Login or register to search.
                                • First post
                                  Last post
                                0
                                • Categories
                                • Recent
                                • Tags
                                • Popular
                                • World
                                • Users
                                • Groups