Update:Remora Migration: Difference between revisions

Line 2: Line 2:


The decision to convert the ''applications_versions.min'' and ''applications_versions.max'' columns from strings into actual foreign keys into the ''appversions'' table presents a conversion problem.  The original min and max version strings in the old database were not closely policed and do not necessarily map to actual application versions.
The decision to convert the ''applications_versions.min'' and ''applications_versions.max'' columns from strings into actual foreign keys into the ''appversions'' table presents a conversion problem.  The original min and max version strings in the old database were not closely policed and do not necessarily map to actual application versions.
''''How do we make a programmatic mapping from fuzzy application version strings to real ones?''''


=== Discussion ===
=== Discussion ===
Line 7: Line 9:
Addon #1980 has two versions (both designated as version 1.0, but that is a different problem).  The first version of the addon is for Firefox 1.0 through 1.6.  Because 1.6 does not exist, migrating that version fails because there is no valid foreign key value for FF1.6.  The second version of this addon is for Firefox 1.0 through 1.5.1.  Well, that version of Firefox doesn't exist either, so that version fails to migrate.
Addon #1980 has two versions (both designated as version 1.0, but that is a different problem).  The first version of the addon is for Firefox 1.0 through 1.6.  Because 1.6 does not exist, migrating that version fails because there is no valid foreign key value for FF1.6.  The second version of this addon is for Firefox 1.0 through 1.5.1.  Well, that version of Firefox doesn't exist either, so that version fails to migrate.


Many of addon version entries have faulty version numbers.
Many addon version entries have faulty version numbers.


Complicating this issue is the incompleteness of the appversions table.  This table is populated by finding the unique entries in the original database's ''applications'' table.   
Complicating this issue is the incompleteness of the appversions table.  This table is populated by finding the unique entries in the original database's ''applications'' table.   
Line 193: Line 195:
|}
|}


''''How do we make a programatic mapping from fuzzy application versions to real ones?''''
 


=== The Solution ===
=== The Solution ===


I'm quite open to having someone give some input into this section.
I'm quite open to having someone give some input into this section.
Confirmed users
675

edits