Web design rates
Naming Consistency We should ensure that a data element that is present in more than one table is represented everywhere by the same column name. In MySQL, a column name does not exist by itself; it is always inside a table. This is why, unfortunately, we cannot pick up consistent column names from, say, a pool of standardized column names and associate it with the tables. Instead, during each table’s creation we indicate the exact column names we want and their attributes. So, let’s avoid using different names internal_number and internal_num when they refer to the same reality. An exception for this: if the column’s name refers to a key in another table the state column and we have more than one column referring to it like state_of_birth, `state_of_residence`. MySQL’s Possibilities versus Portability MySQL permits the use of many more characters for identifiers database, table, and column names than its competitors. The blank space is accepted as are accented characters. The simple trade-off is that we need to enclose such special names with back quotes like ’state of residence’. This procures a great liberty in the expression of data elements, especially for non-English designers, but introduces a state of non-portability because those identifiers are not accepted in standard SQL. Even some SQL implementations only accept uppercase characters for identifiers. I recommend being very prudent before deciding to include such characters. Even when staying faithful to MySQL, there has been a portability issue between versions earlier than 4.1 when upgrading to 4.1. In 4.1.x, MySQL started to represent identifiers internally in UTF-8 code, so a renaming operation had to be done to ensure that no accented characters in the database, table, column and constraint names were present before the upgrade. This tedious operation is not very practical in a 24/7 system availability context. Table Name into a Column Name Another style I often see: one would systematically add the table name as a prefix to ……………………….every………………….. column name. Thus the car table would be comprised of the columns: car_id_number, car_serial_number. I think this is redundant and it shows its inelegance when examining the queries we build: select car_id_number from car is not too bad, but when joining tables we get a query such as select car.car_id_number, buyer.buyer_name from car, buyer
Note: If you are looking for cheap and reliable webhost to host and run your web application check Vision affordable hosting services