Error when editing species page.

[Shovelnose]

@Jools Hey Jools, facing this error message when editing a species page. Have tried with coordinates removed as well, same issue persists.


"General Error
SQL ERROR [ mysqli ]

Data truncated for column 'type_loc_lat' at row 1 [1265]

An SQL error occurred while fetching this page. Please contact the Board Administrator if this problem persists."

Edit : It worked fine in another page where the type locality field wasn't tinkered with. Its probably got to do with the text I am trying to input in the field?

[Jools]

Hi Balaji

It looks like it will be the specific species/data in that species that's not being handled correctly.

Can you tell me which species and what you are altering in which field?

Cheers,

Jools

[Shovelnose]

Hey Jools, the species page was

Glyptothorax siangensis

and the relevant text (type locality) is below.

India, Arunachal Pradesh, Upper Siang District, Siking stream a tributary of Siang River near Yingkiong
(Brahmaputra River drainage), 28°9′ N, 95°00′ E

[Jools]

Hi Balaji,

Bad news I'm afraid. I copied and pasted that into a data sub and it worked. The co-ords (long hand, 28°09'00.0"N 95°00'00.0"E) have got apostrophes as opposed to quotes in them and I thought that might be the problem but no. I had previous ensured that would be translated and work ok.

It could be that in posting to the forum, and then into the data submission, whatever oddity in the data has been removed. Could I ask if you copied and pasted from the paper without any intermediate step? Could I get a copy of the PDF to try if so?

Cheers,


Jools

[Shovelnose]

Hey Jools,

You're right, I did the usual and copy pasted the coordinates onto notepad and then onto the profile.

I've also mailed the relevant paper to you.

[Jools]

Thanks Balaji, I tried various things with the type locality and it all worked fine. Then I figured out the error is caused by removing one or both of the zeros in the default Type Location Latitude or Longitude fields. I think perhaps this is what you did too?

Anyway, I've changed it so if that happens in future it works rather than throw the error message you saw.

Cheers,


Jools