That I'm not sure of Marc, I was only sure that Reactor WOULD choke on the ROWGUIDCOL due to the underlying error that SQL Server would throw. Whether that was the cause of this particular problem I can't tell. You should simply be able to set up a primary key column with a type of uniqueidentifier and a default of newID(), and that part should work. Again, make sure you purge all the Reactor generated CFCs, purge your template cache, and reinitialize Reactor if necessary to make sure it is picking up the new version of the core Reactor components along with any changes you've made to the DB. You normally don't have to do this if you just make DB changes, but since you also updated your core Reactor components, doing a full purge of everything is probably wise.
On 12/12/06, Marc <[EMAIL PROTECTED]> wrote:
I absolutely stand corrected, thank you - ROWGUIDCOL is *NOT* required to have a PK column with uniqueidentifier auto-created by the database on insert. I was somewhat mislead by the BOL text, which lumped ROWGUIDCOL in with the whole topic, as if it were required. I will re-read that documentation That said, will i then run into problems with reactor if I just turn off ROWGUIDCOL, and leave uniqueidentifier with default = newId(), or is there more to it than that? In other words, is it ONLY "ROWGUIDCOL" that reactor was choking on?
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
