Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

mysql ordering

  • 09-01-2007 5:06pm
    #1
    Registered Users, Registered Users 2 Posts: 4,475 ✭✭✭


    Does anybody happen to know what sort of order mysql uses when the ORDER BY field is the same? I have a table with 6 records in it:
    a    1
    b    1
    c    1
    d    1
    e    1
    f    1
    
    if I order by the first field, it's fine, but if I order by the second field, it seems random to me. I thought it would default to the order in which the records were added to the table, but that doesn't appear to be the case. Any clues?


Comments

  • Registered Users, Registered Users 2 Posts: 2,781 ✭✭✭amen


    it the data you are ordering on is the same you are going to get random results (same for any db)
    the order it comes back in may depend on the statistics on the table, the last time a row was updated, the physical storage of the data etc
    basically you shouldn't be ordering on a column if all the data is the same in the column


  • Registered Users, Registered Users 2 Posts: 68,317 ✭✭✭✭seamus


    When duplicates/conflicts occur in the ORDER BY, MySQL does an ORDER BY ASC on the Primary Key.

    I'm not sure what it does if there's no primary key.


  • Registered Users, Registered Users 2 Posts: 4,475 ✭✭✭corblimey


    I have a composite primary key, but it doesn't appear to be using that either.
    the order it comes back in may depend on the statistics on the table, the last time a row was updated, the physical storage of the data etc
    basically you shouldn't be ordering on a column if all the data is the same in the column
    I always assumed it was the order in which the data was added to the table for SQL Server et al. Strange.

    I'll try adding a unique primary key and using that.


Advertisement