[development] Debugging updates

Moshe Weitzman weitzman at tejasa.com
Fri Oct 19 16:59:02 UTC 2007

I haven't used it much, but devel has the ability to store all queries
into the database. see admin/settings/devel. unfortunately,
devel_shutdown() specifically bails on update.php because we used to
output gunk and wreck the JSON thats returned. We should really be
smarter and allow the logging but not allow output to screen. patches

On 10/19/07, Karen Stevenson <karen at elderweb.com> wrote:
> Does anyone have ideas for ways to debug update functions in the install file figure out what's going on when they don't work as expected or when I get reports of problems?
> Is there any way to see the query logs that the devel module creates from within updates? If I use update_sql() I can tell what queries ran, but there are times when I need to use db_query() instead and I can get no clue to what is going on when that runs. And I can't find any way to display messages back to myself or see results of print_r() or any of the other things I do elsewhere to debug scripts.
> I've tried to execute the update() script directly from within a normal page, but that won't work either.
> Ideas welcome!
> Karen

More information about the development mailing list