Hi Pablo, I posted a somewhat similar question a while back, and didn't get closer to a solution.
What I found during my effeorts was that MapInfo runs exclusively in either autocommit mode or manual mode. Autocommit mode is the default, and I found no option to turn this off when running in default mode. But if you employ the statements "Server hdbc Begin Transaction" and "Server hdbc Rollback/Commit", you can control the transaction, but you have to keep using them, even after a commit, which is rather annoying. This mode renders the database connection readonly after a commit, and only allows writing after a new "begin transaction". I ended up caching all sent statements in my own app (in a string array), so nothing is actually sent to Oracle before I issue a commit. That way I have full control, and don't have to rely on any capabilities in Oracle. However, I'm only using Oracle for alpha-numeric access, not spatial. So my approach may not be right - or applicable - to your case. Best regards/Med venlig hilsen Lars V. Nielsen GisPro, Denmark http://www.gispro.dk/ ----- Original Message ----- From: "Pablo Ramos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 08, 2004 2:02 PM Subject: MI-L autocommit and Oracle Spatial hi listers, I have an oracle spatial connection using the toolkit Orainet and what i want is that some sentences that i send to oracle such as inserts, update, etc.. no be commited when i send because i want that all that sentences were commited when i do Server_Execute(connection,"COMMIT"). I have read that there ir an AUTOCOMMIT option but, can i set it off? Anyone can help me? Best regards PABLO --------------------------------- --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 13660
