debugging database writes

[Paul Traina]

As I might have mentioned earlier, I volunteer for a 38 year old non-
profit (sfsi.org) where we take a lot of telephone calls, some from
fairly crazy frequent fliers. I've built a lightweight incoming CRM
system integrated into our phone switch (asterisk) so we can keep
track of callers confidentially and figure out if someone keeps
calling with the same questions/issues. I use tablegear to generate
our reports of switchboard activity, and I also am trying to use it in
"editable cell mode" to clean up log entries when volunteers make
mistakes.

I'm curious how you yourself debug database writes? I've been
disabling the javascript and running with debug enabled (debug and
tablegear-mootools.js caused hanging in "loading" in 1.6.1), and I can
see the database reads, but I never get to see the database write
debug messages because of the screen refresh. I was thinking of just
putting code in to log it to a trace file in /tmp, but was curious if
I was missing something.

I'm having occasional database write failures on only SOME entries.

It's probably because my primary key is a string that looks like a
float (i.e. my primary keys look like 13000000.120) which might get
translated into 1300000.12) by php.

I may need to convert the = to a LIKE, but I wanted to see what TG was
actually doing. Strangely enough, when the .js is disabled, more, but
not all, of the rows are writable. Still investigating as this is low
priority.