Nice. I hadn't read adrian's thread before. If only I'd searched on 'relm' :)<br><br>So if we change the variable table to (system.install): <br><br> db_query("CREATE TABLE {variable} (<br> namespace varchar(128) NOT NULL default ''
<br>
name varchar(128) NOT NULL default '',<br> value longtext NOT NULL,<br> language varchar(12) NOT NULL default '',<br> PRIMARY KEY (namespace, name, language)<br> ) /*!40100 DEFAULT CHARACTER SET UTF8 */ ");
<br><br>We'd be halfway there.<br><br>a patch to variable_get, set, del, and init... in bootstrap.inc and we'd maintain full backward compatibility<br>with the current system, but allow namespace uniqueness and a helper function for mass loading...
<br><br><br><br><div><span class="gmail_quote">On 5/3/07, <b class="gmail_sendername">Moshe Weitzman</b> <<a href="mailto:weitzman@tejasa.com">weitzman@tejasa.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> - we can save extra typing and value passing on variable_get calls<br>> - we have a hook to reuse when we need a list of variables<br>> to present for localization<br>><br>> adds pluses over just using constants.
<br>><br>> Sure, only using constants for default variable values could be make<br>> variable usage better, but I think a hook do more just by being a<br>> central place and not a set of unrelated constants.<br>
<br>i'd like to see this centralized in a hook too. we'll be one step closer to<br>the hierarchy that adrian proposed long ago:<br><a href="http://lists.drupal.org/archives/development/2006-06/msg00309.html">http://lists.drupal.org/archives/development/2006-06/msg00309.html
</a><br></blockquote></div><br><br clear="all"><br>-- <br>-> JV