Composite primary keys require field order to be the same as in model

It appears that composite primary keys need to be declared using field order to be exact like the order of fileds in model declaration.
E.g.

share [mkPersist sqlSettings, mkMigrate "migrateAll"] [persistLowerCase|
Person
    isMail Bool
    name String
    age Int Maybe
    deriving Show
    Primary name isMail
|]

main :: IO ()
main = runSqlite ":memory:" $ do
    runMigration migrateAll

    johnId <- insert $ Person True "John Doe" $ Just 35
    janeId <- insert $ Person False "Jane Doe" Nothing

    people <- selectList [PersonName >. ""] []
    liftIO $ print people

results in

Migrating: CREATE TABLE "person"("is_mail" BOOLEAN NOT NULL,"name" VARCHAR NOT NULL,"age" INTEGER NULL, PRIMARY KEY ("name","is_mail"))
pk-order: ISRManyKeys: unexpected keyvals result: field isMail: Expected Bool, received: PersistText "John Doe"

In out production code we use MySQL and there we get only

fromPersistValuesComposite': keyFromValues failed

from https://github.com/yesodweb/persistent/blob/master/persistent/Database/Persist/Sql/Util.hs#L90 (BTW wasn't removal of errors a point of release 2.7.3.1 of `persistent?)

Also it looks that if primary key fields will be of the same SQL type you could get just incorrect values returned from persistent.
I suppose that persistent should either check that the order of fields is the same or use the correct one itself.

Start in persistent/Database/Persist/Sql/Util.hs around fromPersistValuesComposite' and reproduce the issue with the composite-key Person example using SQLite. Compare the behavior with MySQL and verify that composite primary keys do not depend on model field order or return incorrectly mapped values.