Comments on: Tokyo Cabinet: Beyond Key-Value Store

By: Shane K Johnson » Blog Archive » How I learned to say ‘No’ to SQL

Wed, 30 Sep 2009 14:23:29 +0000

[...] blog post provides additional information with respect to Tokyo Cabinet/Tyrant. And here is the [...]

By: Key/value storage engines « sociomantic labs

Key/value storage engines « sociomantic labs — Tue, 29 Sep 2009 14:13:59 +0000

[...] http://www.igvita.com/2009/02/13/tokyo-cabinet-beyond-key-value-store/ [...]

By: » Tokyo Tyrant PHP, ein Key Value Store taukon.de – PHP und anderer nonsens » Blog Archive

Mon, 14 Sep 2009 17:39:42 +0000

[...] Mehr Details: http://www.igvita.com/2009/02/13/tokyo-cabinet-beyond-key-value-store/ [...]

By: Key Value Store List

Key Value Store List — Sun, 30 Aug 2009 07:20:19 +0000

[...] good intro: Tokyo Cabinet Beyond Key Value Store [...]

By: Key Value Pair Database: Fast Full Text Searches « Mark Evans - Web Consultant

Sun, 23 Aug 2009 20:54:27 +0000

[...] http://www.igvita.com/2009/02/13/tokyo-cabinet-beyond-key-value-store/ [...]

By: tejo

tejo — Tue, 04 Aug 2009 14:58:44 +0000

@John

Thank you John, also for your blog posts!

By: John

John — Tue, 04 Aug 2009 14:28:11 +0000

@tejo

The TC/TT tables are limited to { k => v } hashes where keys and values are strings. If you want to store more structured data, try encoding the values as YAML or using Marshal.dump.

Cheers,

By: tejo

tejo — Tue, 04 Aug 2009 14:24:11 +0000

Hi Ilya, great writeup as usual

Lately I am trying to put some nested data in a tokyo table structure, such as:
t['pk4'] = { ‘name’ => ‘ephrem’, ‘age’ => ‘32′ , ‘colors’=> %w(red white)}

but seems that I can’t…any ideas?

By: coder

coder — Fri, 31 Jul 2009 18:01:39 +0000

There is also Schemafree

http://code.google.com/p/schemafree/

By: Four short links: 31 July 2009 | Tech-monkey.info Blogs

Four short links: 31 July 2009 | Tech-monkey.info Blogs — Fri, 31 Jul 2009 11:08:41 +0000

[...] Tokyo Cabinet: Beyond Key-Value Store — description of Tokyo Cabinet and code examples in Ruby. More on the nosql move to leave relational databases behind for certain modern problems (such as scaling). [...]