Custom drop down list customfieldvalue.NUMBERVALUE shows differently in JIRA issue UI

[Steven Sparks]

When I query 

select * from customfieldvalue
where customfield=(select ID from customfield where cfname='Target Version') AND ISSUE = 1155949;

I get 

# ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE, UPDATED
'52582874', '1155949', '13650', NULL, NULL, '47391.000000', NULL, NULL, NULL, '1573761090209'

When I look in UI I have Target Version : 03.00.00.00

There seems to something that translates 47391.00 to 03.00.00.00 somewhere. 

select * from customfield where id=13650;

# ID, CUSTOMFIELDTYPEKEY, CUSTOMFIELDSEARCHERKEY, cfname, DESCRIPTION, defaultvalue, FIELDTYPE, PROJECT, ISSUETYPE, cfkey
'13650', 'com.atlassian.jira.plugin.system.customfieldtypes:multiversion', 'com.atlassian.jira.plugin.system.customfieldtypes:versionsearcher', 'Target Version', 'The version in which the solution of an issue is planned', NULL, NULL, NULL, NULL, NULL

The question is. What is the table/key paths so I can lookup 47391 to arrive at 03.00.00.00?

[Sébastien Delcoigne]

Sorry for the late answer, I've just stumbled upon this thread today.

The formatting is strange but I would expect the reference of a version to be the id of said version in table PROJECTVERSION. You'd have to perfom a join to fetch the name.

You can find the necessary info in the documentation at https://developer.atlassian.com/server/jira/platform/database-schema/

[Wim van Eupen]

I have exact the same question. For all other custom fields I can get the necessary info.
I also know it's not a good idea to query directly, but in this merger phase it's really necessary ...