[consulting] Question about using Drupal for large searchable database

[Alex Pavlovic]

You didn't indicate how the data is to be searched by users ( what the search fields/options are ). Full text search may not even be necessary depending on your 
requirements.

custom content type should not slow you down and this is a preferred way since you indicated data will be user editable. 

as far as the views go, you can use them or drop in your own queries if you think they are not efficient enough. 
 

>  On 12-05-01 09:25 AM, Sam Cohen wrote:
> This list has sure gone quiet lately.  Is everyone just so busy with work?
> 
>  (Sorry if this isn't the place to ask this.  If anyone knows a better
> place, please advise. )
> 
>  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. 
> 
>  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.  
> 
>  It's a D6 site for a relatively small nonprofit without a lot of traffic.
> 
>  How would you handle it?  Custom module or content type/Views?
> 
>  Thanks,
>  Sam
> 
>  Sam Cohen, Principal
>  New Media Solutions
>  Drupal Training & Services
>  New Courses Starting Soon
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting

-- 
Alex Pavlovic - CEO
Taskforce-1 Industries Ltd.
http://www.taskforce-1.com

Drupal Prometheus MVC is here
http://drupal.org/project/prometheus