Eine Einführung in
|
| SQLite | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to SQLite | ||
| none | ||
| DB2 | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to DB2 | ||
| none | ||
| MS Access | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to MS Access | ||
| N/A. Access is a single user system. | ||
| PostgreSQL | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to PostgreSQL | ||
| The \ commands are not part of SQL, they may be entered in the psql interface to postgres. The given command connects to database "template1" as user "scott". | ||
| Oracle | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to Oracle | ||
| In Oracle this is called a "schema". The new schema is called haggis - it belongs to a user called haggis. | ||
| MS SQL Server | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to MS SQL Server | ||
| The master database includes system tables, many of these are hidden from normal users. | ||
| MySQL | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to MySQL | ||
| none | ||
| Sybase | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to Sybase | ||
| none | ||
| Mimer SQL | ||
| In many engines several independant databases may exist. Often each user has his or her own database. This allows different users to use the same names for tables. | ||
| Specific to Mimer SQL | ||
| none | ||