Today, we’re set to enter phase II of the transition from Mark Logic CEO Blog to Kellblog.
This afternoon, we will cut over to a new blog design. Authoring wise, I will be changing from Blogger as my authoring tool to WordPress, though that shouldn’t directly effect my readers.
I will also be changing the RSS feeds shortly; more on that after the new feeds are up and running.
Also, remember I now tweet from @kellblog, no longer from @ramblingman.
Dave Kellogg is Senior Vice President and General Manager of the Service Cloud at Salesforce.com. From 2004 to 2010, I was CEO at unstructured information leader MarkLogic, taking the company from zero to $80M in run-rate revenues.
Before that, I was CMO at Business Objects as we grew from 250 to over 4,500 people and $30M in revenues to over $1B. Prior to that, I was VP of Marketing at Versant, where we executed a chasm-crossing strategy that resulted in a successful IPO. I started my career in both technical and marketing positions at Ingres.In addition, I sat on the board of big data analytics provider Aster Data until its successful sale to Teradata for $325M. I also do some angel investing and advise the chief executives of several startups.
Read Frequently Asked Questions. Contact Dave.
It is a clever name for naming your blog Kellblog (In French ~ What Blog !).
I spent some time today to read in detail the mechanisms of transaction support in ML.
Apart from the syntax used – this is a very good design.
But I don’t saw a mechanism to perform explicit rollback
Thanks, I must admit the quelle blog homonym was purely accidental, but nevertheless quite fun. As for explicit transaction rollback, I’m not the best guy to ask. I know we support XQuery statements as transactions and that we have the power to back them out (e.g., deadlock). I don’t believe we have an explicit abort statement that the user/programmer can invoke mid-way through.
Jim sent me an email about the question of explicit rollback within a transaction.
I found the solution in the documentation.
In fact the mechanism exists in ML using a pre-commit trigger which can fire an abort of the current transaction.
I’m still not completely outside of the culture SQL !