[wp-hackers] DB options table; useless columns?
computerguru at neosmart.net
Mon Apr 23 12:12:03 GMT 2007
Jeremy Visser wrote:
> Matt Mullenweg wrote:
>> They're legacy from when the options UI was completely auto-generated.
> Well why doesn't the upgrade script delete the columns? Or should it?
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
That would be nice, but unpractical.
The problem is, then it would delete all columns that aren't in the
official schema, making really really hard for some plugins to work
Say I wanted to add a user-specific plugin somewhere that does
something. I could create a new table with the user ID and the set of
options for my plugin (really generic example, I know...), but then
that's just a waste and bad performance.
Better would be to simply add a column to the WP users table, and use it
from there.. Especially if I need access to other WP-core columns too,
not just the ID.
However, I do believe they can be removed with a manual query in the db
delta script, though that would kind of defeat (part of) the purpose of
an automated DB schema updating mechanism....
One question: are these columns created in a _new_ install of WP? That
would be something entirely different.......
More information about the wp-hackers