[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gnutrition] First run of 0.4, revno11
From: |
Jason Self |
Subject: |
Re: [bug-gnutrition] First run of 0.4, revno11 |
Date: |
Sat, 17 Sep 2011 14:25:38 -0400 |
address@hidden wrote:
> 1. "Failed to create file"
> This error message was fixed by manually creating $HOME/.gnutrition/ .
Okay - The program should probably create that directory automatically
if it doesn't exist.
> 2. "SQL error: near "where": syntax error"
> I think that in the function search_contains_proc the following line
> breaks the content of query:
>
> sprintf(query, "%s where Food_Des like \"%s%s%s\"", query, "%",
> search_string, "%");
>
> Before this line is executed, the query variable has this value:
>
> (gdb) print query
> $1 = "select Food_Des from food\000
>
> And after it's executed the value is :
>
> (gdb) print query
> $2 = " where Food_Des like \"%f%\"\000
> .
>
>
> I don't know if you've already fixed them.
Not yet. Revision 11 is the latest.
> I also didn't know if revno 11 was supposed to be tested or not.
That's fine - testing any any point is okay but if you're testing an old
revision and find a bug it's best to check the current revision first and
make sure the bug's still there (just in case later commits fixed it.)
> Is it ok to periodically check for new revisions and test them
> without prior notice
Absolutely.
> (i don't know if there's some automatic way to
> know if new code has been submitted)?
Not currently, but that's not a bad idea. Perhaps there could be a
mailing list where notifications of commits could be sent? Perhaps the
message could contain: Who made the change, what files were changed, and
a diff. I think the Savannah administrators will need to arrange this. I'll
contact them and ask about it.
signature.asc
Description: Digital signature