Database naming conventions for tables and columns:

• Singular table names only (e.g. user, category, product, order, orderProduct)
• Every table must have an auto-incrementing integer column id
• ZF-like names of columns and tables (e.g. user::isAdmin, orderProduct::product)
• Foreign keys must have the same names as reference tables
• SQL keywords are capitalized (e.g. SELECT, INT)

Example of proper SQL file formatting and naming:

CREATE TABLE IF NOT EXISTS `user`
 (
   `id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
   `username` VARCHAR(255) NOT NULL,
   `password` VARCHAR(25) NOT NULL,
   `email` VARCHAR(100) NOT NULL,
   `firstName` VARCHAR(255) NOT NULL,
   `lastName` VARCHAR(255) NOT NULL,
   `dateCreated` DATETIME NOT NULL,
   `userType` INT(11) NOT NULL AUTO_INCREMENT
   `isActive` ENUM('0','1') NOT NULL DEFAULT '1',
   PRIMARY KEY  (`id`),
   UNIQUE KEY `username` (`username`),
   UNIQUE KEY `email` (`email`)
   FOREIGN KEY(`userType`) REFERENCES `userType`(`id`)
        ON UPDATE CASCADE
        ON DELETE CASCADE
 )
 ENGINE=InnoDB
 DEFAULT CHARSET=latin1
 AUTO_INCREMENT=1 ;

Conclusion:
The names of database tables and columns must follow camelLetter as naming conventions.

Dotboost is pleased to announce our North American Relaunch. This new phase comes as a result of dedicated research and analysis on how to best serve clients in Canada and the US.

At the heart of our relaunch is the source release for our exclusive inhouse developed dotKernel framework. We have also added business IT integration and increased the clarity to our existing consulting services.

We’re not your average IT organization; we view our customers as strategic partners. This paradigm allows us to take a comprehensive approach towards creating solutions and gain the competitive advantage.

Founded in 2005, the Dotboost process can incorporate anywhere into your project’s life-cycle including concept development, architecture and design, development and integration, and implementation and support. We use time and distance to our advantage, pushing competitive boundaries and staking our place as a globally efficient organization.

1. Aptana -> Install New Software
2. Add http://update.aptana.com/install/php
3. Then select Aptana PHP and install it.

In case you don’t have yet a SVN plugin, go to

1. Install Aptana Features
2. Others -> Subclipse
3. Follow the instructions

DotKernel Template Engine is an implementation of PHPLib Template engine for PHP5.

It has an amazing ability to separate the application code from the presentation layer. Separates the manipulation of data (in the database as well as in PHP) from its final format, whether that format is HTML, XML or a formatted e-mail. The big advantage is that is allowing us to change the look and feel of a site quickly without having to delve immediately into a lot of PHP variable assignments and print statements.

DotKernel is the DotBoost’s in-house developed framework, based on Zend Framework.
DotKernel is at version 1.0 , released under Open Software License (OSL 3.0) , and is built on top of Zend Framework.

Scienta

We at dotKernel used some very basic debug bar:  queries, time spent , memory used.  But this Scienta is way more complex and nicer then our internal code,  so we switch to it and integrate it in dotKernel code base.

Adobe’s Action Message Format protocol to your PHP 5 application

Download latest  ZF

Also that way we can forget about the need to update ZF at latest versions, and keep tracks of which version and on which server we have ZF.  Of course, backward compatibility  can be an issue in future ZF releases ( like 2.0 branch for PHP > 5.3)

1. Install PEAR if is not installed  already .
2. Follow the instructions for ZF PEAR . Simply use: pear install zend/zend
3. Create a vhosts.conf file in /var/www/vhosts/dotkernel.com/conf  or where is your vhost configuration folder located.
4. In that file, remove the open_basedir :

php_admin_value open_basedir "/var/www/vhosts/dotkernel.com/httpdocs:/tmp:/usr/share/pear"

5. rebuild all vhosts:  /usr/local/psa/admin/sbin/websrvmng -a
6. Restart httpd
7. Call directly the preloader:

    require_once 'Zend/Loader/Autoloader.php';

Solution :

var regex = new RegExp("^[a-z0-9_\+-]+(\.[a-z0-9_\+-]+)*@[a-z0-9-]+(\.[a-z0-9-]+)*\.([a-z]{2,})$","i");

This will validated also emails like: username1+username2@gmail-domain.co.uk

List of dotKernel classes which extend ZF:

1. Template system.

Using Zend_View, which is an interface, we can write our own view class implementing that interface.
We implement our own good-old PHPLIB-style template.

2. Custom Front Controler.

ZF’s default routing like “/controller/action/param1/value1″ need to be customized.
We define our own routing rules and add them to the Front Controller (see ZF Front Controler).
We use some custom routes on our projects.