I initially posted this via the Nabble UI, as it said it would get to the
list. Only - it turns out - if one has already subscribed to the list (and
not just Nabble)! Oops. :-S
Cheers to Doug for pointing me in the right direction last night regarding
getting signed-up to the mailing list properly. I'm getting emails through
now, so seems to be working.
So, anyway, here I am trying again, direct to list this time. Sorry for
repetition.
{quote}
Hi there.
Firstly, I figured this was such a fundamental question that I thought it
*must* be covered already, but I've not been able to find anything (and have
been googling for about an hour!). Sorry if I'm repeating well-trod ground.
I've just started looking at Reactor (in conjunction with Model-Glue and
ColdSpring: I've just finished working through a tutorial series by Ray
Camden he posted a while back: http://tinyurl.com/4dtdv6).
I have to say I'm rather impressed with the whole lot. It seems fairly
straight forward, and makes a great deal of sense. I'm glad people have
taken time to formalise this sort of thing.
I've finished up the work, so I've set Reactor to be in "production" mode
(as I have with ColdSpring too), but Reactor still seems to be hitting the
DB twice for each query: one to query the DB schema, one to perform the
actual query. It's as if it's reading the schema so as to be able to write
the SQL *every time*, rather than just generating/writing the standard
query-SQL the once, and re-using until there's a need to change them.
This leads me to ask two questions:
1) Is there something I'm doing wrong?
2) Does Reactor generate all query SQL statements on the fly, even when in
production mode?
I'm hoping the answers are "yes" and "no" respectively. However I suspect
the answers are the other way around.
Can anyone please set me straight?
Cheers.
{quote}
--
Adam
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[EMAIL PROTECTED]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
