Change 'database' to 'dbname' in db_url and INSTALL.txt

Well,I think INSTALL.txt is fine especially because users do not read it, if they would, then they would have no problem. Now, let's see this version for settings.php

dumb users should use civicspace installer...

Chx's path goes a little too far. I'm ambivalent about this one, honestly, but if it does get switched, at least use "db_name" and not "dbname". The "db_" follows the previously established "standard" of "db_url".

I'm not fond of an array approach. The syntax we're currently using is the "normal" way of indicating database connection information for most database interfaces - I'd rather teach users the "normal" way of marking up their information, such that they can use it in other applications, than teach them PHP arrays.

Users are the ones who edit this files, and they are often not developers. What is obvious for us developers, is totally foreign to others.

I prefer an atomic approach to this: a variable for each component, and we combine them internally to form the database URL.

There is even no need for an array, since users can be confused by the => syntax.

// Database type, either 'mysql' or 'pgsql'
$db_type = 'mysql';
// Database name
$db_name = 'drupal';
// Database user name
$db_user = 'drupal';
// Database password
$db_password = 'secretthing';
// Database host name, normally 'localhost'
$db_host = 'localhost';
// Database port, normally leave it as it is
$db_port = '';

We then combine that to:

$db_url = "$db_type://$db_name:$db_password@db_host/db_name";

I would prefer arrays from anything else. The combination to some URL that anyway needs string parsing afterwards.

$db['type'] = 'mysql';   // Database type, either 'mysql' or 'pgsql'
....

And from the users point of view, I consider this really easy and anyone that configured phpMyAdmin before will also be used to this.

-1 to having the database type be set in an array.

I'm with Morbus. This is what database connection strings look like. The instructions are very clear, and if we change database to db_name, I doubt we can do any better. I don't think setting three variables is easier. I really don't think making a database type variable is a good idea.

If people really can't put the values into the db connection string they should be told to use CivicSpace. In fact, I think all new Drupal users should be told to use CivicSpace.

I hadn't considered the multiple database support aspect. Thanks for pointing that out. If that feature can be supported and this is the path, then I'm a convert.

As for CivicSpace, I recommend to anyone who is interested in Drupal that they check out CivicSpace. I think it is a fantastic product and doesn't lead to people being any less involved with Drupal, but does lead to them being more satisfied with it.

-R

I'm not sure what the point is in changing this. The next statement in the install file explains what "database" is. If we want to go CMS for Dummies, we should work up a web-based installation interaface - and then deal with those headaches.

I recollect that Wordpress follows Khalid's approach. And, we know it is famous for its five-minute install.

Of couse, with command line, I find I can also install drupal in about the same time. But, we are talking about inexperienced users...

Here is more reason for what I suggested in #6 above.

This user is confused with the DB URL and thinks the last fields is a subdirectory.

This stuff is not evident for people, and the installer will not happen for 4.7. Even if the installer is there, it is clearer to have discrete fields, and we join them into a db url.

The core of this issue ('database' to 'dbname') has been addressed via the patch from http://drupal.org/node/25792.