Eine Einführung in
|
| SQLite | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to SQLite | ||
| All data types are ignored, simple strings are used. Given this you should use 'yyyy-mm-dd', your dates will at least be ordered. | ||
| DB2 | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to DB2 | ||
| none | ||
| MS Access | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to MS Access | ||
When used within VBA Access likes dates to be enclosed in hash signs... #20 May 1962# | ||
| PostgreSQL | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to PostgreSQL | ||
| Oracle | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to Oracle | ||
| Oracle can be made to accept almost any format if we use the TO_DATE function. Details at Date Format Elements | ||
| MS SQL Server | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to MS SQL Server | ||
| none | ||
| MySQL | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to MySQL | ||
MySQL only accepts dates in the format yyyy-mm-dd. Be warned that it will accept dates that don't exist - such as 31st September. "30 days hath September..." | ||
| Sybase | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to Sybase | ||
| none | ||
| Mimer SQL | ||
|
The format of dates can be very tricky. Most implementations are fairly robust in what will be accepted - but a date such as 01-02-03 might be interpreted in different ways in different countries. Using a three character month and a four digit year in single quotes (such as '01 Mar 1997') works safely with most systems other than MySQL. | ||
| Specific to Mimer SQL | ||
| none | ||