List:Commits« Previous MessageNext Message »
From:Øystein Grøvlen Date:August 11 2008 12:37pm
Subject:Re: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676)
Bug#38624
View as plain text  
Fix look good, but I am not sure I like the mechanism used in the second 
test case:

> +  DBUG_EXECUTE_IF("backup_fail_add_trigger", DBUG_RETURN(TRUE););
>    if (open_tables(thd, &lst, &num_tables, 0))
> -    DBUG_RETURN(FALSE);
> +    DBUG_RETURN(TRUE);
>  
>    DBUG_ASSERT(num_tables == 1);
>    Table_triggers_list *triggers= lst->table->triggers;

Any particular reason we should test that the code works if TRUE is 
returned from this particular point in this function, and not from all 
the other places that may return TRUE?  I do not think it makes sense to 
add such "error triggers" for all potential errors in the code, so what 
makes this code exceptional?

-- 
Øystein
Thread
bzr commit into mysql-6.0-backup branch (jorgen.loland:2676) Bug#38624Jorgen Loland8 Aug
  • Re: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676)Bug#38624Øystein Grøvlen11 Aug
    • RE: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676) Bug#38624Chuck Bell11 Aug
      • Re: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676)Bug#38624Øystein Grøvlen12 Aug
        • RE: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676) Bug#38624Chuck Bell12 Aug
          • Re: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676)Bug#38624Jørgen Løland13 Aug
            • Re: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676)Bug#38624Øystein Grøvlen13 Aug
              • Re: bzr commit into mysql-6.0-backup branch (jorgen.loland:2676)Bug#38624Jørgen Løland13 Aug