Comments for Toru Maesaka

Comment on How to Recover a Tokyo Cabinet Database by Mark Callaghan

Mark Callaghan — Sun, 21 Mar 2010 15:05:58 +0000

Why do the slides for the successor to Tokyo Cabinet (http://1978th.net/kyotocabinet/) continue to suggest that this provides ACID when it isn’t crash safe?

Comment on DATE type under the hood in Drizzle/MySQL by Madoka

Madoka — Tue, 16 Mar 2010 04:51:17 +0000

hey tooru, do you remember me?
We hanged out a couple of times with shini and dan(?) last year.

I just thought how have you been and emailed you to your cell but
I think the email address has already changed.

Well I hope your doing well,
and maybe we can go out for a drink when you have time!

See ya

Madoka

Comment on Speaking at the MySQL Conference 2010 by Julian

Julian — Fri, 19 Feb 2010 00:18:11 +0000

Hey T,
loved to be there, but not invited and tooo far away… :)
Good luck!
Hope it all goes well!
J

Comment on Cross Posting Woes of Micro Blogging Messages by Blair McBride

Blair McBride — Tue, 09 Feb 2010 03:35:43 +0000

Gotta admit, I’m part of that cross-posting problem. While there’s significant overlap in friends/colleagues/family who use both Twitter and Facebook, there’s also a significant portion who don’t. I rarely pay much attention to Facebook, in part due to the cross-posting (and in part because I dislike Facebook in general). Of course, there are services that act as a client for multiple services (Brizzly, etc), but they seem to be lacking in filtering out duplicates.

Still, its better than having a monoculture.

Comment on Google App Engine and it’s Memcache API by David Gruzman

David Gruzman — Sun, 24 Jan 2010 21:52:27 +0000

I have also measured the memcache performance on the google appengine. Results where somewhat disappointing – since memcache only 2 times faster then datastore. In other hand – published information about memcached outside of google shows much better results then I got on GAE.

Comment on Debugging Drizzle with GDB remotely from OS X by How GDB helped me fix a Drizzle Bug « JZ Talk Blogger

How GDB helped me fix a Drizzle Bug « JZ Talk Blogger — Thu, 21 Jan 2010 02:24:17 +0000

[...] of 4294967295. It was time for some serious GDB’ing. There are a few articles here, here and here that explain how to use gdb and Drizzle, but I start it a little different. Starting GDB and [...]

Comment on Further thoughts on BlitzDB’s Index Handling by Toru Maesaka

Toru Maesaka — Sun, 17 Jan 2010 14:36:00 +0000

@Jay Pipes As always, thanks for the awesome advises! This means a lot to me. I was talking to mtaylor last week and it seems MY_COLLATION_HANDLER object inside MY_CHARSET_INFO has lots of goodies inside it. I'll look into these plus your advise and hopefully solve my problem :)

Comment on Further thoughts on BlitzDB’s Index Handling by Toru Maesaka

Toru Maesaka — Sun, 17 Jan 2010 14:34:06 +0000

@Jobin Augustine Thanks for the encouragement. I think I'll try this approach and see how it goes.

Comment on Drizzle, BlitzDB and HTON_STATS_RECORDS_IS_EXACT by Toru Maesaka

Toru Maesaka — Sun, 17 Jan 2010 14:32:09 +0000

Jay,

That would be neat too. As long as there’s a way for the kernel to directly lookup this information, I have no complaints what-so-ever :)

Comment on Drizzle, BlitzDB and HTON_STATS_RECORDS_IS_EXACT by Jay Pipes

Jay Pipes — Fri, 15 Jan 2010 17:51:32 +0000

IMHO, Cursor::info() is, well, a complete turd-pile of a method. I’d love to get rid of it and use something like:

Cursor *cursor= engine->getCursor(READ_CONSISTENT);
if (engine->supportsExactRowCount())
{
cursor->getRowCount();
}

Much cleaner, IMHO.

-jay