http://www.joinfu.com/2010/03/understanding-drizzles-transaction-log/
On Wed, Mar 17, 2010 at 4:54 PM, Tim Soderstrom <[email protected]> wrote: > *slaps forehead* Didn't even think about UDFs. That's really pretty awesome > and way more fun than just using 'strings' on the file :) > > On Mar 17, 2010, at 2:25 PM, Jay Pipes wrote: > >> So...you haven't figured out the DATA_DICTIONARY views and the custom >> UDFs yet, eh? :) >> >> Hint, try this in a client with the transaction log enabled: >> >> USE DATA_DICTIONARY; >> SELECT PRINT_TRANSACTION_MESSAGE('transaction.log', ENTRY_OFFSET) FROM >> TRANSACTION_LOG_TRANSACTIONS LIMIT 1\G >> SELECT HEXDUMP_TRANSACTION_MESSAGE('transaction.log', ENTRY_OFFSET) >> FROM TRANSACTION_LOG_TRANSACTIONS LIMIT 1\G >> >> :) >> >> -jay >> >> On Wed, Mar 17, 2010 at 3:15 PM, Tim Soderstrom >> <[email protected]> wrote: >>> Hi Jay! >>> >>> Wow I did not think the XA stuff would be done that quickly - that's >>> awesome! Looking forward to those blog articles as well since, other than >>> being able to enable the log, I haven't figured out what else to do with it >>> other than to pipe it through 'strings' and smile :) >>> >>> Tim S. >>> >>> >>> On Mar 17, 2010, at 1:51 PM, Jay Pipes wrote: >>> >>>> Hi Tim! >>>> >>>> I'm putting together some more blog articles about the transaction log >>>> this week, since i just finished up coding the initial XA work. >>>> >>>> I agree with you that transaction_log_log_file sounds silly :) I'll >>>> change it to transaction_log_file in a patch later this week. >>>> >>>> -jay >>>> >>>> On Wed, Mar 17, 2010 at 1:28 PM, Tim Soderstrom >>>> <[email protected]> wrote: >>>>> While playing around with some of the later Drizzle builds, I noticed >>>>> that there are now options for the transaction log and, after a bit of >>>>> trial and error, was able to fire it up. Looks pretty awesome though >>>>> before I get excited with doing further tests, is this feature that is >>>>> something that is ready for testing or feedback? >>>>> >>>>> I didn't want to jump the gun, but I noticed one config variable that >>>>> made me feel icky. 'transaction_log_log_file' sounds pretty redundant. I >>>>> assume the reasoning for that was to emulate a namespace for variables >>>>> related to the transaction log plugin, though I don't think >>>>> 'transaction_log_file' would be unreasonable. >>>>> >>>>> Anyways I apologize if I am jumping into that too soon but it is a >>>>> feature I've been highly excited about and it's nice to see something >>>>> tangible that I can start to play with :) >>>>> >>>>> Tim S. >>>>> _______________________________________________ >>>>> Mailing list: https://launchpad.net/~drizzle-discuss >>>>> Post to : [email protected] >>>>> Unsubscribe : https://launchpad.net/~drizzle-discuss >>>>> More help : https://help.launchpad.net/ListHelp >>>>> >>>> >>> >>> >> > > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
