[development] Huge Database Operation
austin.einter at gmail.com
Mon Mar 7 02:58:49 UTC 2011
I wanted to design/implement similar to monester, where I can handle large
number of users.
But can I have those many users or not, not sure as of now, however it is
good to have a scalable design as a starting point.
Last few months, I have been looking at Drupal, have gone through number of
I am comfortable with Drupal to some extent. Now I want to learn and
implement how to store and retreive data, and what is the best efficient way
when we need to deal with large amount of data.
I just created pages using webform and CCK.
With CCK I see
1. Number of extra field are shown up (like Title, menu settings, input
format etc) and I do not want these fields. Please let me know how can I
stop these fields appearing.
2. I wanted to have a field for resume upload, could not find the FILE field
Then I enabled fileupload module, with this I can see a file upload field in
page. Probably I can look at installing file field.
3. There is a fieldset field in webform to group similar fields under one
group. I am not aware of module which can do this if using CCK. Appreciate
if you can suggest how to keep similar fields in one group.
If I can overcome these issues I am pro for CCK.
Assuming I am going to use CCK, as you mentioned skillset can be indexed
(using custom module), can you kindly provide more information how it can be
done atleast from logic perspective.
On Mon, Mar 7, 2011 at 7:19 AM, nan wich <nan_wich at bellsouth.net> wrote:
> 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 problem.
> 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 here.
> 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
> > 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...
More information about the development