Difference between revisions of "Portable SQL"
From Linuxnetworks
(accessing metadata) |
(triggers) |
||
Line 17: | Line 17: | ||
### [[Portable_SQL/Statements/Access_metadata/Tables|Tables]] | ### [[Portable_SQL/Statements/Access_metadata/Tables|Tables]] | ||
### [[Portable_SQL/Statements/Access_metadata/Table_columns|Table columns]] | ### [[Portable_SQL/Statements/Access_metadata/Table_columns|Table columns]] | ||
+ | ### [[Portable_SQL/Statements/Access_metadata/Triggers|Triggers]] | ||
### [[Portable_SQL/Statements/Access_metadata/Views|Views]] | ### [[Portable_SQL/Statements/Access_metadata/Views|Views]] | ||
# SQL tips | # SQL tips |
Revision as of 14:22, 3 May 2008
The ANSI SQL standard exists for years but it's still difficult to write SQL statements which are portable across most database engine implementations. This guide tries to give you tips about what is possible keeping the most common database implementations in mind and where the limits of portable SQL for this engines are.
Feel free to add your own tips if you like ...
- Common tips
- SQL statements
- SQL tips