Hi, My take on the questions:
- primary key should be uuid and task_id. This is what the task is naturally referenced by when looked up on interrogations. We should not have an Auto field - sstate_result - yes, the value stored in the table should be a small number. ditto for all choice fields - dependent tasks - this should be another table mapping task -> task. - text field Alex On Fri, Jun 7, 2013 at 12:52 PM, Calin Dragomir < [email protected]> wrote: > Hi everyone, > > I've updated the info on the Wiki based on what we've discussed earlier. > The updates are: > > * *task_type* has been replaced with a BooleanField called > *task_executed*which will be True for Executed tasks and False for prebuilt. > I know this > is different from the UI, but having task_type in the DB with the value > True / False was a bit confusing for the readers. If anyone has objections > on this, I can change it back to its original state. > * *task_number* has been replaced by an Integer field called *order *. > * *py_sh* field has been renamed as *script_type* . > * *code* field has been replaced by two fields called *file_path* and * > line_number* . > * *disk_io* has been made a decimal field. > * *task_id* has been added to the set. > * *sstate_result* field has replaced *task_history* and has the 4 options > we have considered. If the current key of the choices is to be changed to > numbers please let me know and I'll modify it. > > There are a couple of questions added at the end of the table, which > should be answered. > > Please review my changes here: > https://wiki.yoctoproject.org/wiki/Django_models > > Thank you, > Calin >
_______________________________________________ webhob mailing list [email protected] https://lists.yoctoproject.org/listinfo/webhob
