View source for SQL injection/Target Environments/Compatibility

<noinclude>:<font size="-2">[[SQL injection]] > [[SQL injection/Target Environments|Target Environments]] > Compatibility</font></noinclude>

For compatibility purposes it is important to be mindful of what functions, environment variables, and tables are ubiquitous.  When writing an automated attack tool, it is convenient to be able to use the same function in each SQL dialect, rather than choosing a function or variable per sql version.

* Additional similarities are added each update to the various database engines.  Read the manuals for the affected engines to get an up-to-date view.
* Not all similarities or differences are documented here, only those relevant to SQL injection.
* Similarities and differences between database engines include table and column names, function names, environment variables, and statement syntax.

There are enough similarities that it is possible to have a degree of '''universal exploitation'''.

===Information_schema===
{{:SQL_injection/Target_Environments/Compatibility/information_schema}}

===Functions & environment variables===
{{:SQL_injection/Target_Environments/Compatibility/functions_and_variables}}

===Other syntax===
{{:SQL_injection/Target_Environments/Compatibility/Other}}

===Capabilities===
{{:SQL injection/Target Environments/Compatibility/Capabilities}}



<noinclude><div style="padding-top:5px; padding-bottom:5px; border-top:1px solid; border-bottom:1px solid; display:inline-block;">'''Currently viewing''' [[SQL injection]] > [[SQL injection/Target Environments|Target Environments]] > Mapping</div></noinclude>