[04:47] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/add-new-processor-api/+merge/185697
[05:58] <StevenK> stub: https://code.launchpad.net/~stevenk/launchpad/db-add-processor/+merge/185700 when you have a tick
[06:03] <stub> StevenK: Surprised we didn't need that earlier.
[06:05] <stub> StevenK: You don't want to add default value and NOT NULL Processor.restricted? It is only 11 rows... Similarly the other new columns - largest table contains 550 rows.
[06:05] <StevenK> stub: NOT NULL will be added in -1
[06:06] <StevenK> stub: The plan is to populate them shortly after that patch is rolled out
[06:06] <wgrant> You can do the NOT NULL for processor if you want, since the app doesn't create them
[06:06] <wgrant> But not for builder
[06:06] <StevenK> We don't touch builder
[06:06] <wgrant> Oh right, builder already has processor
[06:07] <StevenK> Yeah, it's DAS and ArchiveArch
[06:07] <wgrant> But DAS.processor has the same thing
[06:07] <wgrant> And ArchiveArch
[06:07] <wgrant> If you make them NOT NULL initially the test suite will go boom
[06:07] <StevenK> Yes, which is why the -1 DB patch sets them as NOT NULL