another related issue happened when i tried to insert a new record into a MySQL4 table that had an auto-increment primary key set up. the insert called for the primary key to be inserted--overriding the auto-increment setting--quite true, that's not the best way to do it, but mysql allows you to do just that, insert your own primary key rather than accept the auto-incremented primary key. reactor, rather than doing an insert of a new record or throwing an error, attempted to do an update.
i had not designed nor set up the database, but i did have access to turn off auto-increment on the primary key and after turning that off, reactor properly inserted the new record. -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
