You seem to have a habit of inventing bogus SQL and then, when it doesn't work, ask for the correct form on here. If I was the
forum police I would suggest reading some freely available on-line documents, but since I'm not - here's an attempt at answering the
question:
SQL is not a flow-control language, it makes adjustments to (or extractions from) datasets based on relational parameters, some of
which makes it seem very very clever (and indeed I contend that it is quite clever), but it still isn't a flow-control specification.
You will need to decide in your program code whether a Trigger or Index or Table needs to exist or not, and from there instuct SQL
to make it or drop it.
If I may ask, how on Earth did you end up having a Query whereby the creation (or deletion) of entire Triggers becomes part of the
data-execution-logic? Maybe explain the first principle you wish to achieve and we could suggest how to best get there (as many
have done here already).
On 2013/11/01 13:53, techi eth wrote:
How to drop trigger from specific table with condition around?
I tried this but got syntax error.
DROP TRIGGER trigger_name From tbl_name = TestTbl WHERE <Condition>;
Thanks
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
