DB differences between 1.3.0 and 1.4.0 Reference Implementations

[huwsteadCL]

Can you confirm that the point:

'Remove LDH_name in domain and nameserver tables in reference implementation.'

Is the only change to the reference implementation database? (and if so I am assuming that content from the xxx_ldh_name field should instead be populated in the xxx_unicode_name field)

We currently have a draft 1.3.0 solution with data in the reference database and I ideally wanted to retain the existing database content (which should be simple enough if we know the changes)

[TheRedTrainer]

As far as I know, all the changes are the following:

• xxx_ldh_name removed from domain and nameserver (the ldh name is generated from the unicode name). It was removed in order to avoid data duplicity and possible data integrity errors
• a new column vpi_country_code for vcard_postal_info table (in order to allow adding a country code to a vcard postal info, according to requirement 1.4 from ICANN's gTLD RDAP Profile)
• a new table named vcard_contact_uri that allows to add contact uris for a vcard (fulfilling the requirement 2.7.5 from ICANN's gTLD RDAP Profile )

[huwsteadCL]

Thanks for the confirmation.

Just as a note. It looks like https://www.reddog.mx/migration.html needs to be updated to include details of the new table vcard_contact_uri