Fix primary_key_info result ordering #39

Merged
merged 1 commit into from Apr 12, 2013
Commits on Mar 24, 2013
  1. @ilmari

    Fix primary_key_info result ordering

    ilmari committed Mar 24, 2013
    DBI documentation says
    
    > The statement handle will return one row per column, ordered by
    > TABLE_CAT, TABLE_SCHEM, TABLE_NAME, and KEY_SEQ.
    
    But since we're only querying one table the three first ones are by
    definition the same, so it's only necessary to sort by KEY_SEQ.
    
    This happened to come out in the same order on previous versions of
    perl, but as of 5.17.10, hash insertion and traversal order is more
    randomised, so now it fails mos of the time.