Opened 18 years ago
Last modified 8 years ago
#8924 reopened enhancement
autoload should be boolean in add_option()
| Reported by: | jidanni | Owned by: | |
|---|---|---|---|
| Priority: | lowest | Milestone: | Awaiting Review |
| Component: | Database | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
Regarding: CREATE TABLE wp_options (autoload varchar(20) NOT NULL DEFAULT 'yes',
Why not boolean binary, or one character long?
Attachments (1)
Change History (14)
#3
@
15 years ago
Bringing this back up for debate.
Even if we can't make it a boolean or int or something, is there any reason it has no index on it? With options tables inflating due to storage of things like transients and caches, this might be worth indexing.
#4
@
15 years ago
- Resolution wontfix
- Status closed → reopened
I meant to convert add_option() to accept a boolean in #10788, but didn't.
There's little reason to change the storage mechanism, but... I completely forgot it wasn't indexed. Could also consider making it varchar(3).
#6
@
15 years ago
- Summary autoload should be boolean → autoload should be boolean in add_option(), indexed in DB
#8
follow-up:
↓ 11
@
14 years ago
add_option() should accept a boolean. But the DB doesn't need to change (no index, either) — see pento's comment in #14258.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
This is not a trivial change.