This list has sure gone quiet lately. Is everyone just so busy with work?<br><br>(Sorry if this isn't the place to ask this. If anyone knows a better place, please advise. )<br><br>A client of mine with a Drupal site I inherited wants to bring in a very large database into their site. It's basically over 200,000 genealogical/cemetery records that need to be searchable by users. I'm struggling over whether to do it (1) as a custom module, with it's own separate database or (2) to do it with views/content type and node import. The client also needs to be able to edit the records through the site. <br>
<br>The latter approach would be quicker to set up, but I worry that it would bloat the site, potentially cause performance issues, and perhaps other problems I'm not thinking about. <br><br>It's a D6 site for a relatively small nonprofit without a lot of traffic.<br>
<br>How would you handle it? Custom module or content type/Views?<br><br>Thanks,<br>Sam<br><br clear="all">Sam Cohen, Principal<br><a href="http://new-media-solutions.com" target="_blank">New Media Solutions</a><br>Drupal Training & Services<br>
<i><a href="http://new-media-solutions.com/drupal-training" target="_blank">New Courses Starting Soon</a></i><br><a href="http://twitter.com/samcohen" target="_blank"></a><br><div style="display:inline"></div><div style="display:inline">
</div><br>