[development] low hanging fruit for Drupal 6: variable defaults

John Vandervort jvandervort at gmail.com
Thu May 3 15:15:40 UTC 2007

Nice.  I hadn't read adrian's thread before.  If only I'd searched on 'relm'

So if we change the variable table to (system.install):

      db_query("CREATE TABLE {variable} (
        namespace varchar(128) NOT NULL default ''
        name varchar(128) NOT NULL default '',
        value longtext NOT NULL,
        language varchar(12) NOT NULL default '',
        PRIMARY KEY (namespace, name, language)
      ) /*!40100 DEFAULT CHARACTER SET UTF8 */ ");

We'd be halfway there.

a patch to variable_get, set, del, and init... in bootstrap.inc and we'd
maintain full backward compatibility
with the current system, but allow namespace uniqueness and a helper
function for mass loading...

On 5/3/07, Moshe Weitzman <weitzman at tejasa.com> wrote:
> >  - we can save extra typing and value passing on variable_get calls
> >  - we have a hook to reuse when we need a list of variables
> >    to present for localization
> >
> > adds pluses over just using constants.
> >
> > Sure, only using constants for default variable values could be make
> > variable usage better, but I think a hook do more just by being a
> > central place and not a set of unrelated constants.
> i'd like to see this centralized in a hook too. we'll be one step closer
> to
> the hierarchy that adrian proposed long ago:
> http://lists.drupal.org/archives/development/2006-06/msg00309.html

-> JV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070503/a0c6cfa8/attachment.htm 

More information about the development mailing list