[wp-hackers] Plugin best practices: wp_options and storing custom
wordpress at tekartist.org
Thu Apr 3 01:01:44 GMT 2008
Thanks for the feedback guys. It's, as usual, greatly appreciated.
Without laying it too thick, it's close to reason #1 why I like
developing for WP so. :)
So we agree it's not such a bad idea, so long as:
1) I keep the "data sets" relatively small (for table size)
2) I manually set the autoload column off (4th param on add_ and
If so, t's pretty much the best case scenario for me.
Cheers, and back I dive in my code. :)
I'd show it, but the API it integrates with isn't live yet. :p
Soon, soon enough.
Stephane Daury - http://tekartist.org/
On Apr 02, 2008, at 17:40, Viper007Bond wrote:
> Which is best for 99% of cases I think. For the plugin authors that
> they are storing large amounts of data in the options table, they can
> manually turn it off.
> On Wed, Apr 2, 2008 at 2:38 PM, Austin Matzko <if.website at gmail.com>
>> On Wed, Apr 2, 2008 at 5:28 PM, Otto <otto at ottodestruct.com> wrote:
>>> That only gets the options with the autoload column set to "yes".
>>> Other options are only pulled into the cache on an as needed basis.
>> But autoload is "yes" by default. So, plugin authors using the
>> options table for mass data would need to specify that it be off.
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> Viper007Bond | http://www.viper007bond.com/ | http://
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers