dan
|
f380c3f13c
|
Fix a problem caused by using an SQL variable in an OVER clause within a trigger program.
FossilOrigin-Name: 4f676466e60ee2a420b7b2deace76f3a733ce1af278347428285715d9c67f022
|
2021-01-21 15:40:52 +00:00 |
|
drh
|
6ab91a7a7a
|
Add the SQLITE_DEFAULT_DEFENSIVE compile-time option. Fix up test cases
so that they work with DEFENSIVE enabled.
FossilOrigin-Name: 3212733cb6d1a59516d67a86df7c7b1d2456a1b2e5d7080c26b0e87b2609c65d
|
2018-11-07 02:17:01 +00:00 |
|
drh
|
84fbff18d0
|
Prohibit bound parameters in the arguments to table-valued functions within
a trigger. Problem discovered by OSSFuzz.
FossilOrigin-Name: b7178209152452e82f5908513385018524472640d67547927d6b4c0aa0c15a46
|
2018-04-11 16:04:01 +00:00 |
|
drh
|
a23bc8a345
|
From test scripts, remove stray "breakpoint" commands and blank lines
at the ends of files.
FossilOrigin-Name: a6b35273239669189f33402144f58328b133d182
|
2016-02-05 16:46:09 +00:00 |
|
dan
|
46539d7cfa
|
Return an error if an attempt is made to create a trigger with an SQL variable embedded within it. If such a variable reference is found within a trigger definition loaded from the sqlite_master table, silently replace it with a NULL.
FossilOrigin-Name: f35f6ae3da77dbdf5f7a4a9927475659fc6e0ca6
|
2013-10-03 12:29:38 +00:00 |
|