launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #01934
Re: First cut at recipe db-schema patch
Michael Hudson wrote:
> Muharem Hrnjadovic wrote:
>> Michael Hudson wrote:
>> [..]
>>>>>> Comments welcome -- it would be nice to land this this cycle so we can
>>>>>> start working on things for realz next cycle.
>>>>> Screw this part: we can just land it on db-devel. Rushing is bad
>>>> Agreed.
>>> Cool.
>>>
>>> Thanks for the comments! (and sorry for all the typos in my first post).
>>>
>>> There's a new patch at http://pastebin.ubuntu.com/332821/
>> Could you please explain why you have both a SourcePackageBuild and a
>> SourcePackageBuildUpload table? Could the data stored in the latter
>> table not live in the former as well?
>
> Because Julian asked for the ability to upload the output of one recipe
> build to be uploaded to multiple archives.
Hello Michael,
thanks for the explanation. I realized that I probably did not strike
the right note in the other email on the subject, so let me try to amend
by asking a few questions:
What is the advantage of introducing the SourcePackageRecipeData table?
Why not just have a text field where ever that table is referenced?
Why do both SourcePackageRecipe and SourcePackageBuild have a distroseries
foreign key?
Best regards
--
Muharem Hrnjadovic <muharem@xxxxxxxxxx>
Public key id : B2BBFCFC
Key fingerprint : A5A3 CC67 2B87 D641 103F 5602 219F 6B60 B2BB FCFC
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References