---
title: "Important: findAll of contact and profile information orders by uid"
manual: "Academic Profiles"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-persons:important-contact-find-all-orders-by-uid@main"
source: "Changelog/2.4/Important-ContactFindAllOrdersByUid.rst"
rendered: "2026-10-15T10:24:29+00:00"
---

# Important: findAll of contact and profile information orders by uid {#important-contact-find-all-orders-by-uid}

## Description {#description}

The `findAll()` methods of `AddressRepository`,
`EmailRepository`, `PhoneNumberRepository` and
`ProfileInformationRepository` executed without an ordering, so their
result came in whatever order the database yielded. On PostgreSQL that is not
necessarily the same list twice. They now order by `uid` ascending.

The tables are manually sortable, but their `sorting` is kept per contract,
or per profile and type, so it does not order records of different parents
meaningfully. The methods returning the records of one contract or profile
order by `sorting`, with `uid` breaking ties.

## Impact {#impact}

No visible change is expected: nothing in the extensions calls these methods,
and `uid` ascending is the order SQLite, MySQL and MariaDB return in
practice. PostgreSQL promises none. Code that calls them gets that order
guaranteed now rather than by coincidence.

## Affected Installations {#affected-installations}

Installations with own code calling one of these `findAll()` methods.