Perfect. I'll wait for that. I have a question for you.
We have created our own data replication strategy. We have been using it for several years and it works great. Basically we take every "data altering" stored procedure and in the same transaction as it is actually executing, we also insert into another table the sp and parameters. This data is copied to several other servers and executed. We have a class that does all of our database interaction, so it was simple to add this functionality. We are now going to use IBatis for our database interaction. My question is... Is there a way to get a hold of the command object just before or just after you have executed the statement? My plan is to insert some code in the MappedStatement.cs in both the ExecuteUpdate and ExecuteInsert functions that will call out to my code so I can collect the information I need for our replication and insert it to the correct table in the current transaction. I see you have a RaiseExecuteEvent() function available, but it does not pass the command object out. Is there anyway with the current code I can get what I need, or can something like this be added? I don't know if it is of use to the general public to have pre/post processing of a command object? Thanks again for all your help. Mike On 1/5/06, Gilles Bayon <[EMAIL PROTECTED]> wrote: > The [BETA] will be promote as [General Availability] next week. > > Cheers, > -Gilles > > On 1/4/06, Michael Schall <[EMAIL PROTECTED]> wrote: > > Sounds good... Just wanted to make sure we were on the same page. > > > > I will try the latest code. Ideas on how close you are to release? I > > won't be able to try this till next week. > > > > Thanks for your help. > > Mike > > > > On 1/4/06, Gilles Bayon <[EMAIL PROTECTED]> wrote: > > > ThreadStatic is no more use. > > > A source change before the IBATISNET-128 issue have modify how the > > > SqlMapSession is holded. > > > The class SessionHolder.cs have been replace the use of > ISessionContainer. > > > > > > On 1/4/06, Michael Schall < [EMAIL PROTECTED]> wrote: > > > > I was looking over the change log to see what else I would be > > > > upgrading and have a question? > > > > > > > > Are you referring to IBATISNET-128? > > > > > > > > I submitted a patch for that bug and have it in my current build. > > > > > > > > My issue is having multiple transactions on the SAME thread. > > > > > > > > If another fix is in 1.3 for my issue, can you point me to the key? > > > > > > > > Thanks > > > > Mike > > > > > > > > > > >
