Writing Portable SQL
How much portability is worth paying for, which constructs are safe everywhere, and how to isolate the parts that can never be portable.
Differences between SQL products.
5 notes tagged
How much portability is worth paying for, which constructs are safe everywhere, and how to isolate the parts that can never be portable.
One reference table for the differences that actually break code: paging, auto increment, strings, dates, upserts and the features each product lacks.
The two set operations MySQL waited longest to add: rows in both sets, and rows in one set but not the other - plus how to emulate them where they are...
The three joins people meet last: keeping unmatched rows from both sides, deliberate Cartesian products, and joining a table to itself.
Current date and time, adding and subtracting intervals, differences between dates, extracting parts, and formatting - the least portable corner of SQ...