Thanks for all comments & suggestion.
My Point :
If we have trigger creation on per table basis then why can't we have dropping
also on table basis.
It is not good to have feature where each table owner are free to allow the way
he want to create trigger.
I can't quite decipher what you m
On 1 Nov 2013, at 1:15pm, techi eth wrote:
> If we have trigger creation on per table basis then why can't we have
> dropping also on table basis.
TRIGGERs are not related to just one table. You can have a TRIGGER which
mentions any number of tables.
> It is not good to have feature where ea
On Fri, Nov 1, 2013 at 2:15 PM, techi eth wrote:
> It is not good to have feature where each table owner are free to allow the
> way he want to create trigger.
>
sqlite does not offer per-table owners, nor any concept of "owners" at all,
as is clearly stated in the docs:
http://sqlite.org/zeroc
Thanks for all comments & suggestion.
My Point :
If we have trigger creation on per table basis then why can't we have
dropping also on table basis.
It is not good to have feature where each table owner are free to allow the
way he want to create trigger.
On Fri, Nov 1, 2013 at 6:33 PM, RSmit
On 2013/11/01 14:41, techi eth wrote:
I think so checking possible cases of any sqlite operation should not be
called as bogus. Where ever I am not sure I will ask expert help & I have
got all the time right answers.
My point here is (and was) that the SQL you said that you have tried, is complet
On Fri, Nov 1, 2013 at 1:41 PM, techi eth wrote:
> Note: Trigger logic will be different but trigger names are same.
>
No, they won't, because you'll get an error when creating the second
trigger with the same name. There is no per-table namespace for triggers.
It is possible (at least syntactic
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.
I think so checking possible cases of any sqlite operation should not be
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-contro
I don't understand what condition you might be talking about.
As far as I know the functionality only allows you to simply drop a
trigger, in your case:
DROP TRIGGER trigger_name;
or:
DROP TRIGGER IF EXISTS trigger_name;
Best regards,
Daniel
techi eth skrev 2013-11-01 12:53:
How to drop
On Fri, Nov 1, 2013 at 12:53 PM, techi eth wrote:
> DROP TRIGGER trigger_name From tbl_name = TestTbl WHERE ;
>
Google "drop trigger sqlite" says:
http://www.sqlite.org/lang_droptrigger.html
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Since tyranny's
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 ;
Thanks
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/m
11 matches
Mail list logo