Tom,
Suggestion:
Strip rows, triggers and indexes off one by one until it starts working - this
may narrow it down a bit.
Not a bad suggestion; but I can't actually change this table. As I said in the original post, it's part of a licensed third-party application.
I posted the code with the thought that someone might see something in the schema that would cause Reactor's behavior, and thus lead to a fix in Reactor.
But without that, the solution is simply to write a custom query, which I've done. I just thought I might have run across behavior that would cause others problems, too. If I can, I'll work on finding the problem through your method. But I'm still hopeful that someone might be able to see the problem more readily.
--
Thanks,
Tom
Tom McNeer
MediumCool
http://www.mediumcool.com1735 Johnson Road NE
Atlanta, GA 30306
404.589.0560
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
reactor@doughughes.net
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --