RE: Torque is very slow to do a .copy of an object :( Why?

Thanks a lot for all of your answers. Now I understand wh I had duplicate entries in another table ;) I tried to use the function .copy(false) but apparently this one does not exists (I'm using torque 3.2-rc2) :( Alain Greg Monroe wrote: I remember there was a discussion a while back on

AW: Torque is very slow to do a .copy of an object :( Why?

Hi! Could you try a myObject1.copy(false) to avoid making a deepcopy. bye Thoralf I'm using torque to connect to my Mysql database. I'm trying to improve performence of my application and I saw that torque is taking more than 600 ms to execute a command like:

Re: AW: Torque is very slow to do a .copy of an object :( Why?

I tried to use the function .copy(false) but apparently this one does not exists (I'm using torque 3.2-rc2) :( Alain Thoralf Rickert wrote: Hi! Could you try a myObject1.copy(false) to avoid making a deepcopy. bye Thoralf I'm using torque to connect to my Mysql database. I'm

RE: AW: Torque is very slow to do a .copy of an object :( Why?

Hmm, are you using a non-default build option of: torque.complexObjectModel=false That's the only way that the copy( boolean deepcopy) method would not be created in your BaseRecord object. If you are generating your OM layer with this set to false, then doing an OM object .copy() is just a

RE: AW: Torque is very slow to do a .copy of an object :( Why?

Not sure... I can confirm that I do not have the copy(boolean) function but torque is doing a deep copy because when I save my copied object I also get a new entry in the table linked to the original objet. Alain Greg Monroe wrote: Hmm, are you using a non-default build option of: