ok...but what happens when your user base excedes 1000. What would happen to your staging area? How would you assign a unique uid > 1000? How about when your vocab excedes 1000. This is a VERY VERY VERY bad software design move.
<br><br>Scott<br><br>Dave Cohen wrote:<br>> I've started to address this issue by reserving the first 1000 ids for the<br>> "staging" (or if you prefer, "install profile"). So for instance node nid 10
<br>> comes from the install profile, while node nid 1010 is on the production<br>> server only. Same goes for vocabulary with vid 10 (or 1010), menu with mid<br>> 10 (or 1010), etc. Later, I can add node 11 to the install profile and
<br>> propigate it to my production site easily enough and without fear of<br>> overwriting anything that's been configured on the production server.<br>><br>> You can read exactly how I do this here <<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://dave-cohen.com/node/1066" target="_blank">
http://dave-cohen.com/node/1066</a>>.<br><br>> wow, thats a very clever solution to the problem. i would totally support<br>> drupal patches which insure that ids start at 1000. i'm not so sure about a<br>> patch which adds unique keys to all tables. we need someone db person to
<br>> chime in there. anyway, it would be handy if we supported this trick better<br>> (i.e. without patching).<br><br>thanks for sharing.<br><br>-moshe