On 2013.10.15 10:34 PM, Petite Abeille wrote:
On Oct 16, 2013, at 7:20 AM, Darren Duncan wrote:
On 2013.10.14 11:58 PM, Sqlite Dog wrote:
seems like SQLite is not checking trigger SQL for invalid column names
until execution?
What you describe sounds like the
On Oct 16, 2013, at 7:20 AM, Darren Duncan wrote:
> On 2013.10.14 11:58 PM, Sqlite Dog wrote:
>> seems like SQLite is not checking trigger SQL for invalid column names
>> until execution?
>
> What you describe sounds like the behavior of every SQL DBMS which has
>
On 2013.10.14 11:58 PM, Sqlite Dog wrote:
seems like SQLite is not checking trigger SQL for invalid column names
until execution?
What you describe sounds like the behavior of every SQL DBMS which has triggers
whose trigger behavior I know. Seems better to me to retain this behavior than
to
Sqlite Dog wrote:
> seems like SQLite is not checking trigger SQL for invalid column names
> until execution?
No.
> Is there a way to force this check?
Not without compiling the respective INSERT/UPDATE/DELETE statement.
> The problem: trying to find out which indices, triggers and views
Hi,
seems like SQLite is not checking trigger SQL for invalid column names
until execution? Is there a way to force this check?
The problem: trying to find out which indices, triggers and views depend on
particular column. We can recreate table without this column and recompile
indices, triggers
5 matches
Mail list logo