Issue upgrading from 2.31 to 2.32

@stevie Thanks for sharing the table. I was able to find the issue with your data. Some of the coordinate values have some alphabets in between them (Probably a result of some manual import/export).

The affected rows can be seen using the following statement

select * from organisationunit where coordinates ~* '[a-zA-Z]';

There are 15 rows which has coordinates with segments like this [32.q5hODNmn021,-9.744] Looks like a uid has been accidentally injected into some of the coordinate strings.

You will have to correct these corrupted data the way you want it to be, and then retry on the upgrade.

Let us know how it goes.