RE: Question re: Reactor

[Adrian Lynch]

Have you checked the table definitions are the same between dev and staging?
It's possible to import/export/script tables and defaults not to go across
too.

Adrian

 -Original Message-
 From: Nathan Strutz [mailto:str...@gmail.com]
 Sent: 28 July 2009 05:30
 To: cf-talk
 Subject: Re: Question re: Reactor
 
 
 Caroline,
 
 There haven't been very many big changes in Reactor for a few years.
 You
 should update to the latest version and see what breaks. (but no, I
 can't
 confirm that it works or doesn't in SQL2005)
 
 You may be able to win if you just update reactor, (making sure to
 delete
 the cache files in the reactor directory) and refreshing your app...
 
 nathan strutz
 [Blog and Family @ http://www.dopefly.com/]
 [AZCFUG Manager @ http://www.azcfug.org/]
 [Twitter @nathanstrutz]
 
 
 On Mon, Jul 27, 2009 at 4:47 PM, Caroline Wise caracol...@gmail.com
 wrote:
 
 
   We have a rather old application that uses an early version of
 Reactor
  (vintage 2006-ish). It works fine with SQL 2000 in the development
  environment. We don't get many change requests for this app so while
 it
  gets
  a lot of use in the production environment, things on dev and staging
 are
  pretty quiet. Recently I had to make an extremely minor content
 update and
  it turned out that the staging box version had an issue inserting a
 new
  user, a problem we could not duplicate in development or production.
 
  When I compared the the Reactor code it turned out that it was
 different
  for
  this part of the application. The user table is using some defaults
 and
  they
  were not picked up in the Reactor code. The client, who has control
 over
  the
  staging environment, updated the database to SQL 2005 some time ago
 and my
  suspicion is that our version of Reactor can't cope.
 
  I'm wondering if anyone out there is using a newer version of Reactor
 and
  can confirm that it works fine with SQL 2005. Also of course I'm
 trying to
  gauge the risk and effort involved with updating Reactor to that
 newer
  version. Would I have to replace the whole thing or are we talking
 about
  something akin to a plugin for 2005?
 
  Thanks in advance for your insights,
 
 
  Caroline Wise


~|
Want to reach the ColdFusion community with something they want? Let them know 
on the House of Fusion mailing lists
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325028
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Re: Question re: Reactor

[Nathan Strutz]

Caroline,

There haven't been very many big changes in Reactor for a few years. You
should update to the latest version and see what breaks. (but no, I can't
confirm that it works or doesn't in SQL2005)

You may be able to win if you just update reactor, (making sure to delete
the cache files in the reactor directory) and refreshing your app...

nathan strutz
[Blog and Family @ http://www.dopefly.com/]
[AZCFUG Manager @ http://www.azcfug.org/]
[Twitter @nathanstrutz]


On Mon, Jul 27, 2009 at 4:47 PM, Caroline Wise caracol...@gmail.com wrote:


  We have a rather old application that uses an early version of Reactor
 (vintage 2006-ish). It works fine with SQL 2000 in the development
 environment. We don't get many change requests for this app so while it
 gets
 a lot of use in the production environment, things on dev and staging are
 pretty quiet. Recently I had to make an extremely minor content update and
 it turned out that the staging box version had an issue inserting a new
 user, a problem we could not duplicate in development or production.

 When I compared the the Reactor code it turned out that it was different
 for
 this part of the application. The user table is using some defaults and
 they
 were not picked up in the Reactor code. The client, who has control over
 the
 staging environment, updated the database to SQL 2005 some time ago and my
 suspicion is that our version of Reactor can't cope.

 I'm wondering if anyone out there is using a newer version of Reactor and
 can confirm that it works fine with SQL 2005. Also of course I'm trying to
 gauge the risk and effort involved with updating Reactor to that newer
 version. Would I have to replace the whole thing or are we talking about
 something akin to a plugin for 2005?

 Thanks in advance for your insights,


 Caroline Wise


 

~|
Want to reach the ColdFusion community with something they want? Let them know 
on the House of Fusion mailing lists
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325023
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4