[support] Saving and Retreiving Form Data

[Metzler, David]

Either are possible.  I've used both, mostly postgres for its rich
feature set, but mysql for web applications that don't care about a rich
database feature set. 

 

If you don't plan to be a database administrator MySQL is probably a
better choice, but then, if your going to be loading million plus row
tables, you might want a DBA or learn how to be one.  MySQL out of the
can typically outperforms postgres, but Postgres has more performance
tuning features, and so if you were interested in controlling things
like physical storage based on  application keys, Postgres is a better
bet. 

 

In drupal 6, you'll get stronger drupal support in MySQL.  I think the
jury is still out on postgres. 

 

My point really was to not advise you on which to use, but to warn you
against designing storage optimization in PHP applications.   That is
something that's best done in the DB layer

 

Dave

________________________________

From: Austin Einter [mailto:austin.einter at gmail.com] 
Sent: Monday, March 07, 2011 3:32 PM
To: support at drupal.org
Cc: Metzler, David
Subject: Re: [support] Saving and Retreiving Form Data

 

Metzler

Thanks for advice. 

Out of all databases as of now Drupal is compatible with, which one is
suitable for high row counts and better performance during search, is it
postgres? Currently I am using MySQl (5.5.8), will it scale up to high
row counts.

 

Best Regards

Austin

 


 

On Mon, Mar 7, 2011 at 9:42 PM, Metzler, David <metzlerd at evergreen.edu>
wrote:

I would advise against that. 

 

Drupal.org is hosting probably over 500,000 users already and there
hasn't been a noticeable performance problem with logging in. Modern
databases such as Postgres work fine with large row counts.  They
support feature like partitioning to make sure that the data is stored
in separate places on disk based the value of  key fields.   Don't make
the mistake of thinking that in PHP you can out optimize a database
written for such activities. An index of 7 million integer uids is still
a pretty small file by todays standards.  Solve performance problems
when and where they happen, and throw hardware and or database server
feature sets at the problem rather than trying to out-program the DB
programmers. 

 

The account profile is serialized data so I wouldn't store it there,
particularly if you want to be querying it, but you can write a custom
module to store info that is not natively in the user table there. 

 

 

 

________________________________

From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On
Behalf Of Kamal Palei
Sent: Sunday, March 06, 2011 3:07 PM
To: support at drupal.org
Cc: adept techlists - kazar
Subject: Re: [support] Saving and Retreiving Form Data

 

Thanks Kazar

This option may not be suitable as the number of records are going to be
quite high.

Probably user name should be hashed and on that basis table name should
be selected to store, seach data for better performance.

I really appreciate your information, this is really usefull for small
to medium scale operations.

 

Regards

Austin

On Mon, Mar 7, 2011 at 4:15 AM, adept techlists - kazar
<techlists at ade.pt> wrote:

On 3/6/11 4:37 PM, Austin Einter wrote:
> Thanks Kazar
> Just one quick question.
> All users, user profile data etc are stored in a single table in
> Database or per user one table is created.
> Is there any limit for maximum number of users.

There is a single "users" table

As far as I know there is no limit (but I am far from expert at Drupal),
other than hardware and memory settings that will need to be sufficient
if you have many users logged in at once.

kazar


>
> On Sat, Mar 5, 2011 at 7:24 PM, adept techlists - kazar

> <techlists at ade.pt <mailto:techlists at ade.pt>> wrote:
>
>     On 3/3/11 9:56 PM, Austin Einter wrote:
>     > Hi All
>     > I have a requirement, where I need to have a form and expected
>     fields
>     > are -
>     > Name
>     > Contact number
>     > Email ID
>     > Resume (File upload)
>

>     Why not just add fields to the user's account profile? This way
>     the info
>     can be retrieved and updated by them (or viewed/edited by site
>     admin or
>     other users depending on permissions)
>
>     If you upgrade to Drupal 7 you can add fields to the user profile
(see
>     "Administer User Profile" http://drupal.org/node/874026 ). This is
>     part
>     of the core install and requires no further modules.
>
>     For Drupal 6 there is the Profile module (see
>     http://drupal.org/node/23710 )
>
>

--

[ Drupal support list | http://lists.drupal.org/ ]

 


--
[ Drupal support list | http://lists.drupal.org/ ]

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20110307/023121f1/attachment.html