Re:MySQL now includes memcached, and a plugin that allows fa...
by sopooneo on Friday August 03, 2012 @10:29AM
(#4334156)
Why have an m2m table? Just have a table with two columns: post_id (or whatever is being tagged) and tag (varchar). If you want to present a list of possible tags just query for uniques. I may be missing something, so please correct me if there is a better way or I am misunderstanding your point.
Re:MySQL now includes memcached, and a plugin that allows fa...
by est on Friday August 03, 2012 @10:54AM
(#4334280)
there are three design patterns for tags in a table based db
Re:MySQL now includes memcached, and a plugin that allows fa...
by ericcoleman on Friday August 03, 2012 @03:25PM
(#4335686)
Link is dead... Just redirects to dev.mysql.com
Cache link, since I can't find it on dev.mysql.com:
http://webcache.googleusercontent.com/search?q=cache:II_A7LF...
Re:MySQL now includes memcached, and a plugin that allows fa...
by geon on Friday August 03, 2012 @06:56AM
(#4333472)
I believe Postgres supports something like that.
Re:MySQL now includes memcached, and a plugin that allows fa...
by fdr on Friday August 03, 2012 @11:44PM
(#4337449)
One might choose to use the array datatype, combined with GiST, GIN, and/or expression based indexes, depending on the workload. That would be somewhat more lucid in most situations than a string packed into an attribute.
However, I wish there's something in reverse: Redis as a MySQL storage engine. The most obvious useful things is that you can save a `tags` table without m2m tables, juse use Redis sets.