Great post Matt,
Can you update the users here what does two settings do?
Gracias
Great post Matt,
Can you update the users here what does two settings do?
Gracias
While you’re at it, can you put mine to bed too. It’s 1 am and she’s not the least bit tired.
~Brad
Well then shouldn’t it be the other way around and be off by default, seeing as the default for session flushing in the Application.cfc is true? Or do I have that wrong as well L
Regards,
Andrew Scott
Then answer this Matt.
If I try every combination of these settings
flushatrequestend = false,
automanageSession = false
or
flushatrequestend = true,
automanageSession = false
or
flushatrequestend = false,
automanageSession = true
or
flushatrequestend = true,
automanageSession = true
And I don’t have the following
var tx = ORMGetSession().beginTransaction();
try{
entitySave(arguments.entity, arguments.forceInsert);
tx.commit();
}
catch(Any e){
tx.rollback();
throw(e);
}
Are you saying that it will fail on some of the above configurations? I have tried them all without the transaction block and it works the same regardless. So if it is a must to do this, I am still not understanding it. The proof I have seen and played with says it is not needed if you are only saving one entity.
Regards,
Andrew Scott
Thanks for the quick turn around on the changes Luis, they look good.
Hope you got some sleep.
.brett
Not really, baby was up and up until 1am