I have a couple of problems with the extendeddata table. Can someone enlighten me on this please. If an object's data does not fit in the objects table, it is spread out into different sections in the extendeddata table. So far so good. When an object is read back, a <cfa_recordSelect> is performed on the ExtendedData table. The resulting query does not contain an 'order by' statement, so in theory the segments could arrive back in any order, resulting in invalid wddx packets. Why this does not happen in real life I do not know. What I do know is that things will go very very badly wrong when it does happen. Second, suppose an object is updated by two people at the same time. Both updates cause the object to grow beyond the maximum size. What happens is that both updates then try to insert a row into the extendeddata table. Of course the second insert then fails. I have already seen this happen, so this is a real problem. Also I do not see any form of transactional protection, like <cftransaction> when extendeddata is updated. All in all, this whole extendeddata thing looks to me like a *major* accident just waiting to happen. Any comments? Cheers Michiel -- Michiel Boland <[EMAIL PROTECTED]> Digital Valley Internet Professionals Plantsoen 17, Wageningen, The Netherlands Phone: +31 317 465555, Fax: +31 317 460276 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
