Coding standards

Just a heads up that I've been working on something of interest to this group. I am making a 'code beautifier' module privately for use by my company - we have some peculiar standards like '3 spaces' for a tab - and I know I will be inconsistent due to me switching between Drupal and other standards.

The idea is that it is a web form that you fill in and it gives you the code you need, all formatted and indented nicely.

The following two things are well known conventions but I was unable to find any documentation on d.o for them:

1. Sub-Module names.
   These are modules within modules (which are really projects on d.o). The convention, as I understand it is: {core_module_name}_{sub_module}. This basically ensures that no sub-modules will use the same namespace as contributed modules or sub-modules.
2. Function Names.
   We know that all hooks have to be prefixed with the module name, but it is only common practice to make any other public or private function prefixed with module name (as well as the leading underscore (_) for "private" functions): {module_name}_{action}. Again, this basically handles name collisions with other contributed modules. This standard could also include how to form function names, for example as suggested by webchick: {module_name}_{verb}_{thing_being_verbed}

So, what I need from this great group is:

1. Are these agreed upon standards?
2. Where is the best place for this documentation?
   There is: Module Development, but even under that, there is no general module development guidelines (instead of specific version)
   And: Standards and Security
   Or: some other.

Neither PEAR nor we define a clear coding-standard for the logical negation operator ("!" as in !$foo). However, to my knowledge, all of Drupal core + contrib is using:

In a code clean-up issue for Better Formats module, dragonwize proposed to use a space between the operator and following code, as we do with the concatenation operator and arithmetic operators:

Coder Tough Love is a companion to the existing Coder module by Doug Green, and its initial development has been sponsored by Trellon. Unlike Coder, which strives to follow the documented style guidelines of Drupal core, Coder Tough Love takes the tougher tactic of applying finely aged and obsessively anal wisdom from years of Drupal development and persnickety quality control.

We should figure out and document a standard for this, then roll a patch to make it consistent.

Please see: http://drupal.org/node/331951

I was just wondering if we have, or if we should have, any SQL coding standards regarding whitespace usage. For example, should we be using a space between column names in IN where clauses or have spaces on either side of comparison operators, etc.

Here are some examples to illustrate what I mean:

Hi all,
I'm at the documentation sprint.
I would like to propose some CSS coding standards, to accompany the PHP coding standards, along with the proposed Javascript standards.

I've added a handbook page at
http://drupal.org/node/302199
Discussion should be in this thread, and the handbook page updated as necessary.

Stella, the Coder module maintainer, has promised to add this to Coder module, once the dust settles on the dissussion.

Drupal and MySQl located in two different servers:

Configuration: Drupal server: Dual core processor, 4GB RAM
MySQL Server: Xeon Processor, 4GB RAM

MySQL Enterprise edition 5

In an exercise to Pre populate the database with 1 million records, record insertions in the tables are very slow since the requests are getting queued up in the database. Insertion is done using a special tool that records our drupal application and plays back the scripts in a loop to populate the database.

Please see the below data collected by the team.