[development] Huge Database Operation

nan wich nan_wich at bellsouth.net
Mon Mar 7 01:49:25 UTC 2011

Does even Monster have a resume for 1 out of every five people in the US? I 
doubt it seriously. I'm guessing that you would have to service every country in 
the world to get that many, and then translation would to be your biggest 

If you use CCK, I believe you can get the skillset indexed for search (at the 
very least in a custom module). I don't know why Webform would be preferable 

A custom module could probably invoke PHP's zipping functions to zip going into 
the database and unzip it coming back out.

I see this over and over: A newbie thinks their first Drupal project should be 
the next Monster. I am sorry to tell you, but you won't get there. Go and focus 
on some smaller projects to learn Drupal. If it has to be done now, you need to 
hire a team, and that's big bucks.
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.

From: Larry Garfield

Assuming your number is in fact 70 million records

The degree to which you need to manage that data through Drupal rather than 
just search it is also a major factor.  

From: pm Austin Einter wrote:
> Hi
> I am looking at storing huge data in database (approximately 70,000,00
> records).
> Each record consists of
> 1. Name
> 2. Contact number
> 3. Resume (may vary from 50KB to 150KB)
> 4. Skill set
> And when a user(having role based permission) wants to search database and
> retreive those user's record having certain skill set, should able to
> perform as quick as possible and show it in a view.
> For front end interface I am looking at webform. Do you have a better
> suggestion please recomond.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20110306/f6554ccb/attachment-0001.html 

More information about the development mailing list