User login

Storing lots of little pieces of data for a module: best practices? Interim practices?

How to store a bunch of little variables?

Location.module does it this way, a separate, dynamically produced variable for every field and node type. The value is either 0 (don't display), 1 (display), or 2 (required)

      $workflow_setting = variable_get('location_'. $field_name .'_'. $node->type, $field_name == 'country' ? 1 : 0);

One thing that worries us about the variable variable approach -- agaric_example_module_prefix_variable_node_type_here -- is that there's no really clean way of deleting them all.

I'm encasing it in a function to make it easier for Agaric to change later

think that's best...

Resolution

Comments

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.