orderBy doesn't work laravel in one table











up vote
0
down vote

favorite












I'd like to sort my data by using orderby in Laravel. Here is my code:



History::where('cus_id', $id)
->orderBy('updated_at', 'DESC')
->get();


History table migration



public function up()
{
if(!Schema::hasTable('history')) {
Schema::create('history', function (Blueprint $table) {
$table->increments('id');
$table->string('name', 255)->nullable();
$table->string('cus_id', 40)->nullable();
$table->string('activity', 255)->nullable();
$table->string('remark_id', 4)->nullable();
$table->integer('user_id')->unsigned()->nullable();
$table->string('note', 255)->nullable();
$table->timestamps();
});
}
}


the result is not according to orderby










share|improve this question
























  • try using the lowercase 'desc'
    – Eric Marcelino
    Nov 22 at 2:17










  • Can you post your create history table migration?
    – Peter
    Nov 22 at 2:20










  • @EricMarcelino the results are the same, not in the order
    – ialx
    Nov 22 at 2:36










  • @Peter history table migration above
    – ialx
    Nov 22 at 2:37










  • @ialx what version of laravel you are using?
    – Eric Marcelino
    Nov 22 at 2:43















up vote
0
down vote

favorite












I'd like to sort my data by using orderby in Laravel. Here is my code:



History::where('cus_id', $id)
->orderBy('updated_at', 'DESC')
->get();


History table migration



public function up()
{
if(!Schema::hasTable('history')) {
Schema::create('history', function (Blueprint $table) {
$table->increments('id');
$table->string('name', 255)->nullable();
$table->string('cus_id', 40)->nullable();
$table->string('activity', 255)->nullable();
$table->string('remark_id', 4)->nullable();
$table->integer('user_id')->unsigned()->nullable();
$table->string('note', 255)->nullable();
$table->timestamps();
});
}
}


the result is not according to orderby










share|improve this question
























  • try using the lowercase 'desc'
    – Eric Marcelino
    Nov 22 at 2:17










  • Can you post your create history table migration?
    – Peter
    Nov 22 at 2:20










  • @EricMarcelino the results are the same, not in the order
    – ialx
    Nov 22 at 2:36










  • @Peter history table migration above
    – ialx
    Nov 22 at 2:37










  • @ialx what version of laravel you are using?
    – Eric Marcelino
    Nov 22 at 2:43













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'd like to sort my data by using orderby in Laravel. Here is my code:



History::where('cus_id', $id)
->orderBy('updated_at', 'DESC')
->get();


History table migration



public function up()
{
if(!Schema::hasTable('history')) {
Schema::create('history', function (Blueprint $table) {
$table->increments('id');
$table->string('name', 255)->nullable();
$table->string('cus_id', 40)->nullable();
$table->string('activity', 255)->nullable();
$table->string('remark_id', 4)->nullable();
$table->integer('user_id')->unsigned()->nullable();
$table->string('note', 255)->nullable();
$table->timestamps();
});
}
}


the result is not according to orderby










share|improve this question















I'd like to sort my data by using orderby in Laravel. Here is my code:



History::where('cus_id', $id)
->orderBy('updated_at', 'DESC')
->get();


History table migration



public function up()
{
if(!Schema::hasTable('history')) {
Schema::create('history', function (Blueprint $table) {
$table->increments('id');
$table->string('name', 255)->nullable();
$table->string('cus_id', 40)->nullable();
$table->string('activity', 255)->nullable();
$table->string('remark_id', 4)->nullable();
$table->integer('user_id')->unsigned()->nullable();
$table->string('note', 255)->nullable();
$table->timestamps();
});
}
}


the result is not according to orderby







php laravel






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 at 9:29









P. Ellul

400314




400314










asked Nov 22 at 2:10









ialx

135




135












  • try using the lowercase 'desc'
    – Eric Marcelino
    Nov 22 at 2:17










  • Can you post your create history table migration?
    – Peter
    Nov 22 at 2:20










  • @EricMarcelino the results are the same, not in the order
    – ialx
    Nov 22 at 2:36










  • @Peter history table migration above
    – ialx
    Nov 22 at 2:37










  • @ialx what version of laravel you are using?
    – Eric Marcelino
    Nov 22 at 2:43


















  • try using the lowercase 'desc'
    – Eric Marcelino
    Nov 22 at 2:17










  • Can you post your create history table migration?
    – Peter
    Nov 22 at 2:20










  • @EricMarcelino the results are the same, not in the order
    – ialx
    Nov 22 at 2:36










  • @Peter history table migration above
    – ialx
    Nov 22 at 2:37










  • @ialx what version of laravel you are using?
    – Eric Marcelino
    Nov 22 at 2:43
















try using the lowercase 'desc'
– Eric Marcelino
Nov 22 at 2:17




try using the lowercase 'desc'
– Eric Marcelino
Nov 22 at 2:17












Can you post your create history table migration?
– Peter
Nov 22 at 2:20




Can you post your create history table migration?
– Peter
Nov 22 at 2:20












@EricMarcelino the results are the same, not in the order
– ialx
Nov 22 at 2:36




@EricMarcelino the results are the same, not in the order
– ialx
Nov 22 at 2:36












@Peter history table migration above
– ialx
Nov 22 at 2:37




@Peter history table migration above
– ialx
Nov 22 at 2:37












@ialx what version of laravel you are using?
– Eric Marcelino
Nov 22 at 2:43




@ialx what version of laravel you are using?
– Eric Marcelino
Nov 22 at 2:43












3 Answers
3






active

oldest

votes

















up vote
0
down vote



accepted










With the code you provided, I think that everything should work properly.



It's hard to understand what's happening in there with this few code, so here is what you can do:




  • In the History model, please make sure that you don't have public property $timestamps set to false

  • Still in the History model, add protected $table = 'history'.
    The default behaviour of Laravel will make Eloquent looks into the histories table, not history.

  • Your migration starts with if(!Schema::hasTable('history')), make sure that everything updated properly.


Hope it helps.






share|improve this answer




























    up vote
    1
    down vote














    The orderBy method allows you to sort the result of the query by a
    given column. The first argument to the orderBy method should be the
    column you wish to sort by, while the second argument controls the
    direction of the sort and may be either asc or desc =>



    Here is the solution for you =>




     $users = DB::table('history')
    ->where(['cus_id'=>$id])
    ->orderBy('updated_at', 'desc')
    ->get();



    If you are using model then,




    History::where('cus_id',$id)->orderBy('updated_at','desc')->get();





    share|improve this answer






























      up vote
      0
      down vote













      Why don't you try some alternate solution?

      Use sortbyDesc method, I confirmed from documentation that it is available for your version of Laravel(5.4).



      Here goes your code:



      History::where('cus_id', $id)
      ->get()
      ->sortbyDesc('updated_at');





      share|improve this answer























      • This still doesn't answer why orderBy is not working. To me, it would be cleaner to have everything handled in one single query than to fetch data and to map the Collection afterward.
        – P. Ellul
        Nov 22 at 4:43











      Your Answer






      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "1"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422957%2forderby-doesnt-work-laravel-in-one-table%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote



      accepted










      With the code you provided, I think that everything should work properly.



      It's hard to understand what's happening in there with this few code, so here is what you can do:




      • In the History model, please make sure that you don't have public property $timestamps set to false

      • Still in the History model, add protected $table = 'history'.
        The default behaviour of Laravel will make Eloquent looks into the histories table, not history.

      • Your migration starts with if(!Schema::hasTable('history')), make sure that everything updated properly.


      Hope it helps.






      share|improve this answer

























        up vote
        0
        down vote



        accepted










        With the code you provided, I think that everything should work properly.



        It's hard to understand what's happening in there with this few code, so here is what you can do:




        • In the History model, please make sure that you don't have public property $timestamps set to false

        • Still in the History model, add protected $table = 'history'.
          The default behaviour of Laravel will make Eloquent looks into the histories table, not history.

        • Your migration starts with if(!Schema::hasTable('history')), make sure that everything updated properly.


        Hope it helps.






        share|improve this answer























          up vote
          0
          down vote



          accepted







          up vote
          0
          down vote



          accepted






          With the code you provided, I think that everything should work properly.



          It's hard to understand what's happening in there with this few code, so here is what you can do:




          • In the History model, please make sure that you don't have public property $timestamps set to false

          • Still in the History model, add protected $table = 'history'.
            The default behaviour of Laravel will make Eloquent looks into the histories table, not history.

          • Your migration starts with if(!Schema::hasTable('history')), make sure that everything updated properly.


          Hope it helps.






          share|improve this answer












          With the code you provided, I think that everything should work properly.



          It's hard to understand what's happening in there with this few code, so here is what you can do:




          • In the History model, please make sure that you don't have public property $timestamps set to false

          • Still in the History model, add protected $table = 'history'.
            The default behaviour of Laravel will make Eloquent looks into the histories table, not history.

          • Your migration starts with if(!Schema::hasTable('history')), make sure that everything updated properly.


          Hope it helps.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 22 at 4:38









          P. Ellul

          400314




          400314
























              up vote
              1
              down vote














              The orderBy method allows you to sort the result of the query by a
              given column. The first argument to the orderBy method should be the
              column you wish to sort by, while the second argument controls the
              direction of the sort and may be either asc or desc =>



              Here is the solution for you =>




               $users = DB::table('history')
              ->where(['cus_id'=>$id])
              ->orderBy('updated_at', 'desc')
              ->get();



              If you are using model then,




              History::where('cus_id',$id)->orderBy('updated_at','desc')->get();





              share|improve this answer



























                up vote
                1
                down vote














                The orderBy method allows you to sort the result of the query by a
                given column. The first argument to the orderBy method should be the
                column you wish to sort by, while the second argument controls the
                direction of the sort and may be either asc or desc =>



                Here is the solution for you =>




                 $users = DB::table('history')
                ->where(['cus_id'=>$id])
                ->orderBy('updated_at', 'desc')
                ->get();



                If you are using model then,




                History::where('cus_id',$id)->orderBy('updated_at','desc')->get();





                share|improve this answer

























                  up vote
                  1
                  down vote










                  up vote
                  1
                  down vote










                  The orderBy method allows you to sort the result of the query by a
                  given column. The first argument to the orderBy method should be the
                  column you wish to sort by, while the second argument controls the
                  direction of the sort and may be either asc or desc =>



                  Here is the solution for you =>




                   $users = DB::table('history')
                  ->where(['cus_id'=>$id])
                  ->orderBy('updated_at', 'desc')
                  ->get();



                  If you are using model then,




                  History::where('cus_id',$id)->orderBy('updated_at','desc')->get();





                  share|improve this answer















                  The orderBy method allows you to sort the result of the query by a
                  given column. The first argument to the orderBy method should be the
                  column you wish to sort by, while the second argument controls the
                  direction of the sort and may be either asc or desc =>



                  Here is the solution for you =>




                   $users = DB::table('history')
                  ->where(['cus_id'=>$id])
                  ->orderBy('updated_at', 'desc')
                  ->get();



                  If you are using model then,




                  History::where('cus_id',$id)->orderBy('updated_at','desc')->get();






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 25 at 8:14

























                  answered Nov 25 at 8:07









                  Prathamesh

                  263117




                  263117






















                      up vote
                      0
                      down vote













                      Why don't you try some alternate solution?

                      Use sortbyDesc method, I confirmed from documentation that it is available for your version of Laravel(5.4).



                      Here goes your code:



                      History::where('cus_id', $id)
                      ->get()
                      ->sortbyDesc('updated_at');





                      share|improve this answer























                      • This still doesn't answer why orderBy is not working. To me, it would be cleaner to have everything handled in one single query than to fetch data and to map the Collection afterward.
                        – P. Ellul
                        Nov 22 at 4:43















                      up vote
                      0
                      down vote













                      Why don't you try some alternate solution?

                      Use sortbyDesc method, I confirmed from documentation that it is available for your version of Laravel(5.4).



                      Here goes your code:



                      History::where('cus_id', $id)
                      ->get()
                      ->sortbyDesc('updated_at');





                      share|improve this answer























                      • This still doesn't answer why orderBy is not working. To me, it would be cleaner to have everything handled in one single query than to fetch data and to map the Collection afterward.
                        – P. Ellul
                        Nov 22 at 4:43













                      up vote
                      0
                      down vote










                      up vote
                      0
                      down vote









                      Why don't you try some alternate solution?

                      Use sortbyDesc method, I confirmed from documentation that it is available for your version of Laravel(5.4).



                      Here goes your code:



                      History::where('cus_id', $id)
                      ->get()
                      ->sortbyDesc('updated_at');





                      share|improve this answer














                      Why don't you try some alternate solution?

                      Use sortbyDesc method, I confirmed from documentation that it is available for your version of Laravel(5.4).



                      Here goes your code:



                      History::where('cus_id', $id)
                      ->get()
                      ->sortbyDesc('updated_at');






                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Nov 22 at 8:58









                      P. Ellul

                      400314




                      400314










                      answered Nov 22 at 3:34









                      Rahul Gurung

                      6711




                      6711












                      • This still doesn't answer why orderBy is not working. To me, it would be cleaner to have everything handled in one single query than to fetch data and to map the Collection afterward.
                        – P. Ellul
                        Nov 22 at 4:43


















                      • This still doesn't answer why orderBy is not working. To me, it would be cleaner to have everything handled in one single query than to fetch data and to map the Collection afterward.
                        – P. Ellul
                        Nov 22 at 4:43
















                      This still doesn't answer why orderBy is not working. To me, it would be cleaner to have everything handled in one single query than to fetch data and to map the Collection afterward.
                      – P. Ellul
                      Nov 22 at 4:43




                      This still doesn't answer why orderBy is not working. To me, it would be cleaner to have everything handled in one single query than to fetch data and to map the Collection afterward.
                      – P. Ellul
                      Nov 22 at 4:43


















                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Stack Overflow!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422957%2forderby-doesnt-work-laravel-in-one-table%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Trompette piccolo

                      Slow SSRS Report in dynamic grouping and multiple parameters

                      Simon Yates (cyclisme)