#relationaldatabase

In DBMS, a tuple refers to a single row in a table, representing a complete record of related data. Each tuple contains fields or attributes that correspond to table columns. Tuples are fundamental to relational databases and help organize and retrieve structured information efficiently Read More...

MySQL database courses  is an open-source relational database management system (RDBMS) based on Structured Query Language (SQL). It is used to store, manage, and retrieve data for websites and applications. MySQL is known for its speed, reliability, and ease of use, and is widely used with web technologies, especially PHP.

Key Features:

Relational database: Organizes data in tables with rows and columns.

SQL support: Uses SQL for querying and managing data.

Open-source: Free to use under the GNU General Public License (GPL).

Cross-platform: Runs on Windows, Linux, macOS, etc.

Scalable: Suitable for both small and large applications.

Secure: Supports user access control and encryption.

Common Uses:

Websites (e.g., with WordPress, Joomla)

Web apps (e.g., e-commerce, blogs)

Data warehousing

Logging systems                                                                                                                                                                                    📞 Phone Number: +91 9511803947                                                                                                                                              📧 Email Address: [email protected]    

What is MySQL?

MySQL is a freely available open source Relational Database Management System (RDBMS) that uses Structured Query Language (SQL). SQL is the most popular language for adding, accessing and managing content in a database. It is most noted for its quick processing, proven reliability, ease and flexibility of use.

What is a naming convention?

In computer programming, a naming convention is a set of rules for choosing the character sequence to be used for identifiers that denote variables, types, functions, and other entities in source code and documentation.

General rules — Naming conventions

Using lowercase will help speed typing, avoid mistakes as MYSQL is case sensitive.

Space replaced with Underscore — Using space between words is not advised.

Numbers are not for names — While naming, it is essential that it contains only Alpha English alphabets.

Valid Names — Names should be descriptive of the elements. i.e. — Self-explanatory and not more than 64 characters.

No prefixes allowed.

Database name convention

Name can be singular or plural but as the database represents a single database it should be singular.

Avoid prefix if possible.

MySQL table name

Lowercase table name

MySQL is usually hosted in a Linux server which is case-sensitive hence to stay on the safe side use lowercase. Many PHP or similar programming frameworks, auto-detect or auto-generate class-based table names and most of them expect lowercase names.

Table name in singular

The table is made up of fields and rows filled with various forms of data, similarly the table name could be plural but the table itself is a single entity hence it is odd and confusing. Hence use names like User, Comment.

Prefixed table name

The table usually has the database or project name. sometimes some tables may exist under the same name in the database to avoid replacing this, you can use prefixes. Essentially, names should be meaningful and self-explanatory. If you can’t avoid prefix you can fix it using php class.

Field names

Use all above cases which include lowercase, no space, no numbers, and avoid prefix.

Choose short names no-longer than two words.

Field names should be easy and understandable

Primary key can be id or table name_id or it can be a self-explanatory name.

Avoid using reserve words as field name. i.e. — Pre-defined words or Keywords. You can add prefix to these names to make it understandable like user_name, signup_date.

Avoid using column with same name as table name. This can cause confusion while writing query.

Avoid abbreviated, concatenated, or acronym-based names.

Do define a foreign key on database schema.

Foreign key column must have a table name with their primary key.

e.g. blog_id represents foreign key id from table blog.

Avoid semantically — meaningful primary key names. A classic design mistake is creating a table with primary key that has actual meaning like ‘name’ as primary key. In this case if someone changes their name then the relationship with the other tables will be affected and the name can be repetitive losing its uniqueness.

Conclusion