search

RBGE-Herbarium / Specify_forms

For files required for the editing of forms within Specify
1 stars 0 forks source link

Specify needs to be updated from 6.4.04 to 6.8 #2

Closed redrinkwater closed 4 years ago

redrinkwater commented 4 years ago

The server copy of Specify needed to be updated to the latest version.

redrinkwater commented 4 years ago

Email to Martin:

Hi Martin,

I hope you are well.

During the break from the migration work, there has been an update to Specify (v. 6.8). This includes some additional fields that we requested.

I haven’t yet updated the version of Specify running on the server, as I was unsure if there would be any impacts on the migration work you have been carrying out. Ahead of the work on the migration restarting this needs to be completed. Could you let me know whether it is something you are happy to do, or if it is something I can carry out.

I have updated the local copy I have and found that it was quite a long process (1hour+), the agents table seemed to take most of this time. This is where the additional fields were added, so this may be the reason.

Best wishes

Robyn

Response from Martin:

Hi Robyn

If you perform the upgrade on the server copy then I will take a backup of that and replace it as the basis for the migration.

When I restart the work I will run the upgrade on my local copy of Specify as well.

I assume that this is a general upgrade and is available from Specify and not an RBGE specific configuration tweak as performed before.

Cheers Martin

Issue with upgrade process - email to Martin:

Hi Martin,

I have started the process of upgrading to the latest version, but I’m hitting an error. It is unable to complete as it can’t change the field type of Geography>FullName to varchar(500) from varchar(255). The error is:

Specified key was too long; max key length is 767 bytes.

It seems to be to do with the collation of the database, which is currently latin1. Is it possible to change this (maybe to utf8mb4), or was there a reason for using this particular collation?

Thanks for your help

Robyn

Hi Robyn

I did not explcitily set the collation for the Schema which does indeed appear to be latin1 - this should not be a problem however since the character set and the collation for the individual tables is set to utf-8.

The problem will actually be the MySQL version which is currently 5.6 and which sets a maximum key length in its indexes of 767 bytes.

I recommend you upgrade to 5.7 (NOT 8) and then try and run the specify upgrade again.

Do you have the necessary permissions to do this or should I do it for you?

Cheers Martin

redrinkwater commented 4 years ago

This has solved the issue and the Specify copy was able to be updated