Sha256: 91f196ab6ccded7f0d6752b4c3f7f44ed00f820a899cc6847588f400bcc970b6
Contents?: true
Size: 1.36 KB
Versions: 12
Compression:
Stored size: 1.36 KB
Contents
These test cases cover obfuscation (more properly, masking) of literal values from SQL statements captured by agents. SQL statements may be captured and attached to transaction trace nodes, or to slow SQL traces. Input queries end with the suffix `.sql`, and the expected obfuscated results end with the suffix `.obfuscated`. Input queries may contain comment lines explaining notes about the test case. Comment lines will precede the actual query, and begin with a `#` symbol. Test cases that have a `.mysql` or `.postgres` tag in the filename preceding the `.sql` suffix are specific to either mysql or postgres obfuscation. This is relevant because PostgreSQL uses different identifier and string quoting rules than MySQL (most notably, double-quoted string literals are not allowed in PostgreSQL, where double-quotes are instead used around identifiers). The `malformed` directory contains SQL queries that are not valid SQL in any quoting mode. Some agents may choose to attempt to obfuscate these cases, and others may instead just replace the query entirely with a placeholder message. The following database documentation may be helpful in understanding these test cases: * [MySQL String Literals](http://dev.mysql.com/doc/refman/5.5/en/string-literals.html) * [PostgreSQL String Constants](http://www.postgresql.org/docs/8.2/static/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS)
Version data entries
12 entries across 12 versions & 1 rubygems