Drupal multi-site sequence issue

Submitted by hpn on June 24, 2007 - 21:31
Notes

Add new comment

The content of this field is kept private and will not be shown publicly.

Filtered HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
If you are running a Drupal multi-site installation, and the sequence tables are shared, then here's an admonition: take real care of the changed prefix for each shared database. Cross check on the sequence tables if you ever had to rename the database or just the unshared tables. For instance, [dbprefix_dbname] becomes [dbprefixnew_dbname] The first thing you have to do is go check the sequence table and change the values manually on the new sequence table entries corresponding to the database appropriately. If you've ever had to change the database name on a live production site that gets significant visitors each minute, it might as well be a good idea to avoid the change! :)