Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-14 Thread Adrian Klaver
On 01/14/2016 01:47 PM, Williamson, Michael wrote: Please excuse my mistake. We were dropping a view that had the trigger on it beforehand, then in trying to re-build the entire schema had scripts that attempted to drop trigger if they existed before re-creating the view and triggers. I over-sa

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-14 Thread Williamson, Michael
Please excuse my mistake. We were dropping a view that had the trigger on it beforehand, then in trying to re-build the entire schema had scripts that attempted to drop trigger if they existed before re-creating the view and triggers.  I over-sanitized the example I posted and made it unclear. I

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread Adrian Klaver
On 01/13/2016 03:25 PM, Williamson, Michael wrote: Ccing list Is that happening on all triggers you are trying to DROP, or just this one? All, consistently. If just this one, you might want to check to see if the trigger was created with a quoted mixed case name and therefore needs to have

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread David Rowley
On 14 January 2016 at 12:08, Adrian Klaver wrote: > On 01/13/2016 02:51 PM, David Rowley wrote: > >> On 14 January 2016 at 11:32, Adrian Klaver > > wrote: >> >> On 01/13/2016 02:24 PM, Tom Lane wrote: >> >> "Williamson, Michael" >

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread Adrian Klaver
On 01/13/2016 02:51 PM, David Rowley wrote: On 14 January 2016 at 11:32, Adrian Klaver mailto:adrian.kla...@aklaver.com>> wrote: On 01/13/2016 02:24 PM, Tom Lane wrote: "Williamson, Michael" mailto:michael.william...@tamucc.edu>> writes: I'm attempting to drop a trigger

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread David Rowley
On 14 January 2016 at 11:32, Adrian Klaver wrote: > On 01/13/2016 02:24 PM, Tom Lane wrote: > >> "Williamson, Michael" writes: >> >>> I'm attempting to drop a trigger that may or may not exist, so am using >>> the "IF EXISTS" clause. Â This works fine for tables, views, functions, >>> domains, a

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread Adrian Klaver
On 01/13/2016 02:24 PM, Tom Lane wrote: "Williamson, Michael" writes: I'm attempting to drop a trigger that may or may not exist, so am using the "IF EXISTS" clause. Â This works fine for tables, views, functions, domains, and types, but for some reason seems to be ignored for triggers. Â I'd e

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread Adrian Klaver
On 01/13/2016 02:14 PM, Williamson, Michael wrote: I'm attempting to drop a trigger that may or may not exist, so am using the "IF EXISTS" clause. This works fine for tables, views, functions, domains, and types, but for some reason seems to be ignored for triggers. I'd expect to see more about

Re: [GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread Tom Lane
"Williamson, Michael" writes: > I'm attempting to drop a trigger that may or may not exist, so am using > the "IF EXISTS" clause.  This works fine for tables, views, functions, > domains, and types, but for some reason seems to be ignored for > triggers.  I'd expect to see more about this online

[GENERAL] v9.1, DROP TRIGGER IF EXISTS behaving oddly

2016-01-13 Thread Williamson, Michael
I'm attempting to drop a trigger that may or may not exist, so am using the "IF EXISTS" clause.  This works fine for tables, views, functions, domains, and types, but for some reason seems to be ignored for triggers.  I'd expect to see more about this online if it were a bug, so I'm thinking I may