Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
wp-hackers
Home
+ new post
About this group
Join this group
Message from discussion 2.4 Feature Proposal: New general meta-data table
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Otto  
View profile  
 More options Oct 4 2007, 7:41 pm
From: Otto <o...@ottodestruct.com>
Date: Thu, 4 Oct 2007 18:41:46 -0500
Local: Thurs, Oct 4 2007 7:41 pm
Subject: Re: [wp-hackers] 2.4 Feature Proposal: New general meta-data table
Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author
On 10/4/07, Omry Yadan <o...@yadan.net> wrote:

> I don't think putting the options there would be a good idea.

> many users understand the options table and know how to change values
> there manually.

> putting it into a generic metadata table will make wordpress much more
> opaque to users.

Bah. Good database design waits not for users manually editing things!
Plugins will no doubt adapt (or not notice, if they're using the add
and remove options functions).

On 10/4/07, Andy Skelton <skelt...@gmail.com> wrote:

> At first glance, this does not look like a good move. It would seem to
> confuse things.

> However, if you consider the blog as an object with the implicit ID of
> 1, it makes perfect sense. Taking it further, into the context of
> WPMU, there is a blogs table where each blog has an ID and a sites
> table where each site has an ID.

That was my basic line of thought, yeah. The options table is nothing
more than key/value pairs tied to a blog_id. For MU, this also means
that options can be fully separated without wacky option naming
conventions.

Pretty much any table you care to create is going to have some kind of
unique ID field. If it then contains key/value pairs, it can fit into
this meta table design, as long as it also has a unique meta_type. The
meta_type could even be as simple as the name of the other table that
the meta_id is referring to.
_______________________________________________
wp-hackers mailing list
wp-hack...@lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-hackers


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google