Tokyto Cabinet Table engine?

13 views
Skip to first unread message

nanook

unread,
Aug 29, 2009, 2:31:43 PM8/29/09
to LightCloud
I'm currently researching Tokyo Cabinet, Tyrant and Lightcloud and I'm
very intrigued by what I'm seeing so far. I noticed that Tokyo Cabinet
has a table engine (http://www.igvita.com/2009/02/13/tokyo-cabinet-
beyond-key-value-store/) that looks to be very useful to do SQL-type
of queries. Does Lightcloud have the ability to make use of these?

spacelee

unread,
Aug 29, 2009, 10:03:29 PM8/29/09
to LightCloud
lightcloud can also do this if the tyrant has provided the table API.
maybe next time i will add some features for the table in lightcloud-
php.

nanook

unread,
Aug 29, 2009, 10:20:43 PM8/29/09
to LightCloud
Wow, that would be really neat! I would certainly be interested in
seeing that feature in lightcloud-php! Is that a difficult thing to
implement?

amix

unread,
Aug 30, 2009, 5:27:43 AM8/30/09
to light...@googlegroups.com
I would discourage this usage, as a real relational database (e.g.
MySQL/PostgreSQL) are much better fits than LC/TT.

Amir

2009/8/30 spacelee <fjc...@gmail.com>:

nanook

unread,
Aug 30, 2009, 8:03:10 AM8/30/09
to LightCloud
Could you elaborate on why you would discourage this? I understand
that no key-value database is designed to be a complete replacement
for RDMS databases and that it's recommended to use MySQL/PostgreSQL
alongside these systems. But at the same time it would seem to me that
the table engine is one of the main advantages that Tokyo Cabinet has
over other solutions, so why not make use of it?

On Aug 30, 3:27 am, amix <ami...@gmail.com> wrote:
> I would discourage this usage, as a real relational database (e.g.
> MySQL/PostgreSQL) are much better fits than LC/TT.
>
> Amir
>
> 2009/8/30 spacelee <fjct...@gmail.com>:

amix

unread,
Aug 30, 2009, 8:43:32 AM8/30/09
to light...@googlegroups.com
The table support in Tokyo Cabinet is one of the recent additions and
_not_ one of the main reasons why one would use Tokyo Cabinet. One
should use Tokyo Cabinet because of such things like _great_
performance, battle tested key-value store and good tool support
(e.g. Tokyo Tyrant).

Anyhow, I follow the philosophy of using the best tool for the job and
Tokyo Cabinet isn't the best tool for storing and manging relational
data. If you need this, then pick MySQL or Postgre - you are likely to
hit a lot less problems than using a recent feature of Tokyo Cabinet.

Regards,
amix

2009/8/30 nanook <asn...@hostonfiber.com>:

Spacelee

unread,
Aug 30, 2009, 10:10:49 PM8/30/09
to light...@googlegroups.com
i agree with amix...

2009/8/30 amix <ami...@gmail.com>



--
Spacelee
Reply all
Reply to author
Forward
0 new messages