[flexcoders] Re: LCDS + CF : How can I change bean's property of new version on creation?
Thank you for replay! I can't do that. Because the value is actually timestamp to detect confliction. Therefor the value should be changed after creation. h ok, I have to change something thanks Shigeru Nakagaki --- In flexcoders@yahoogroups.com, João Fernandes [EMAIL PROTECTED] wrote: Shigeru, when you create new items , a refill is made to your collection and it will compare it with the previous fill, so since you didn't update the hoge property, it won't be reflected in your refill. If you do this instead cfset new.hoge = 123 cfset new = dao.create(new) cfset co.setNewVersion(new) cfset co.processed() your hoge will be committed to the db and will be reflected in the result of the fill. -- João Fernandes Adobe Community Expert http://www.onflexwithcf.org http://www.riapt.org Portugal Adobe User Group (http://aug.riapt.org)
Re: [flexcoders] Re: LCDS + CF : How can I change bean's property of new version on creation?
Shigeru, so that property is a read only property?is it just a timestamp for conflict resolution? You shouldn't need that since that's what the sync method is all about, to detect possible conflicts and throw them. How could your bean at creation be in a conflict anyway? João Fernandes Adobe Community Expert http://www.onflexwithcf.org http://www.riapt.org Portugal Adobe User Group (http://aug.riapt.org)
[flexcoders] Re: LCDS + CF : How can I change bean's property of new version on creation?
Sorry, I was half asleep :D It never conflict on creation. I tried your way. cfset new.hoge = 123 cfset new = dao.create(new) cfset co.setNewVersion(new) cfset co.processed() But hoge of result data was NOT changed although the debugged data was changed on server-side. However identity value (auto incrementation) was updated. hmmm... Am I missing some setting to work this? thanks Shigeru Nakagaki --- In flexcoders@yahoogroups.com, João Fernandes [EMAIL PROTECTED] wrote: Shigeru, so that property is a read only property?is it just a timestamp for conflict resolution? You shouldn't need that since that's what the sync method is all about, to detect possible conflicts and throw them. How could your bean at creation be in a conflict anyway? João Fernandes Adobe Community Expert http://www.onflexwithcf.org http://www.riapt.org Portugal Adobe User Group (http://aug.riapt.org)
