<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Where possible, do everything in code rather than the database. Trying to merge two databases is a giant </div><div>pain, but pushing new code and running update.php is fairly painless.</div><div><br></div><div>If you do have to make database changes after the client has already entered data, you'll want to script it (often</div><div>using an importer).</div><div><br></div><div>- Ken Winters</div><br><div><div>On Jan 29, 2010, at 11:47 AM, Stewart Birch wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello all<br><br>very early on in my Drupal learning process but have been asked to come up with a solution where the client will be entering content on the production site and we may very well be making structural changes ( css etc ) <br> on DEV and changes to the site setup ( for example a page name or somesuch ) , is there a way to seperate the data entered for content types from everything else so when deploying a site to production we can do so without worrying about content being lost.<br> <br>Thanks<br><br>Stewart<br><br><br><br><br><a href="http://www.flickr.com/people/mrbirch">http://www.flickr.com/people/mrbirch</a><br></blockquote></div><br></body></html>