[04:47] wgrant: https://code.launchpad.net/~stevenk/launchpad/add-new-processor-api/+merge/185697 [05:58] stub: https://code.launchpad.net/~stevenk/launchpad/db-add-processor/+merge/185700 when you have a tick [06:03] StevenK: Surprised we didn't need that earlier. [06:05] 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] stub: NOT NULL will be added in -1 [06:06] stub: The plan is to populate them shortly after that patch is rolled out [06:06] You can do the NOT NULL for processor if you want, since the app doesn't create them [06:06] But not for builder [06:06] We don't touch builder [06:06] Oh right, builder already has processor [06:07] Yeah, it's DAS and ArchiveArch [06:07] But DAS.processor has the same thing [06:07] And ArchiveArch [06:07] If you make them NOT NULL initially the test suite will go boom [06:07] Yes, which is why the -1 DB patch sets them as NOT NULL === tasdomas_afk is now known as tasdomas === tasdomas is now known as tasdomas_afk === tasdomas_afk is now known as tasdomas === Guest8446 is now known as wedgwood === tasdomas is now known as tasdomas_afk === _mup__ is now known as _mup_ === bigjools_ is now known as bigjools