Strange error when including one Output Channel in another...

Hi ho,

I received this strange error message recently (1.10.3) when
adding  
one Output Channel to another Output Channel.



An error occurred while processing your request:

Unable to execute SQL statement

DBD::Pg::st execute failed: ERROR:  duplicate key violates
unique  
constraint "udx_output_channel_include"
  [for Statement "
             INSERT INTO output_channel_include (id,
output_channel__id,
                                                
include_oc_id)
             VALUES(NEXTVAL('seq_output_channel_include'),
?, ?)
         " with ParamValues: 2='1025', 1='1024'] at
/home/domain/ 
bricolage/lib/Bric/Util/DBI.pm line 1083, <GEN1498>
line 1869.
Please report this error to your administrator.



However, the first OC was successfully included in the
second OC.  
Thoughts?

Phillip.

--
Phillip Smith,
Simplifier of Technology
Community Bandwidth

On Oct 23, 2007, at 07:02, Phillip Smith wrote:

> DBD::Pg::st execute failed: ERROR:  duplicate key
violates unique  
> constraint "udx_output_channel_include"
>  [for Statement "
>             INSERT INTO output_channel_include (id,  
> output_channel__id,
>                                                
include_oc_id)
>            
VALUES(NEXTVAL('seq_output_channel_include'), ?, ?)
>         " with ParamValues: 2='1025', 1='1024'] at
/home/domain/ 
> bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN1498> line 1869.
> Please report this error to your administrator.
>
>
>
> However, the first OC was successfully included in the
second OC.  
> Thoughts?

Either it was already in the OC and you didn't realize
(though how  
the UI didn't know that I couldn't tell you), or somehow the
callback  
tried to add it twice (though it would happen every time if
that were  
the case).

Might you have already added it in another browser?

Best,

David

On Oct 23, 2007, at 1:17 PM, David E. Wheeler wrote:

> On Oct 23, 2007, at 07:02, Phillip Smith wrote:
>
>> DBD::Pg::st execute failed: ERROR:  duplicate key
violates unique  
>> constraint "udx_output_channel_include"
>>  [for Statement "
>>             INSERT INTO output_channel_include (id,
 
>> output_channel__id,
>>                                                
include_oc_id)
>>            
VALUES(NEXTVAL('seq_output_channel_include'), ?, ?)
>>         " with ParamValues: 2='1025',
1='1024'] at /home/domain/ 
>> bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN1498> line 1869.
>> Please report this error to your administrator.
>>
>>
>>
>> However, the first OC was successfully included in
the second OC.  
>> Thoughts?
>
> Either it was already in the OC and you didn't realize
(though how  
> the UI didn't know that I couldn't tell you), or
somehow the  
> callback tried to add it twice (though it would happen
every time  
> if that were the case).

Odd. I tried it again and there was / is no problem to
report.

> Might you have already added it in another browser?

Nope. Not as far as I know.

--
Phillip Smith,
Simplifier of Technology
Community Bandwidth

On Wed, 24 Oct 2007, Phillip Smith wrote:
> On Oct 23, 2007, at 1:17 PM, David E. Wheeler wrote:
>> On Oct 23, 2007, at 07:02, Phillip Smith wrote:
>>> DBD::Pg::st execute failed: ERROR:  duplicate
key violates unique 
>>> constraint
"udx_output_channel_include"
>>> [for Statement "
>>>            INSERT INTO output_channel_include
(id, output_channel__id,
>>>                                               
include_oc_id)
>>>           
VALUES(NEXTVAL('seq_output_channel_include'), ?, ?)
>>>        " with ParamValues: 2='1025',
1='1024'] at 
>>> /home/domain/bricolage/lib/Bric/Util/DBI.pm
line 1083, <GEN1498> line 
>>> 1869.
>>> Please report this error to your
administrator.

Is it an upgraded system?

On Oct 29, 2007, at 10:46 AM, Scott Lanning wrote:

> On Wed, 24 Oct 2007, Phillip Smith wrote:
>> On Oct 23, 2007, at 1:17 PM, David E. Wheeler
wrote:
>>> On Oct 23, 2007, at 07:02, Phillip Smith
wrote:
>>>> DBD::Pg::st execute failed: ERROR: 
duplicate key violates  
>>>> unique constraint
"udx_output_channel_include"
>>>> [for Statement "
>>>>            INSERT INTO
output_channel_include (id,  
>>>> output_channel__id,
>>>>                                            
   include_oc_id)
>>>>           
VALUES(NEXTVAL('seq_output_channel_include'), ?, ?)
>>>>        " with ParamValues: 2='1025',
1='1024'] at /home/domain/ 
>>>> bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN1498> line 1869.
>>>> Please report this error to your
administrator.
>
> Is it an upgraded system?

Yes. From 1.10.2

--
Phillip Smith,
Simplifier of Technology
Community Bandwidth

On Tue, 30 Oct 2007, Phillip Smith wrote:
> On Oct 29, 2007, at 10:46 AM, Scott Lanning wrote:
>> On Wed, 24 Oct 2007, Phillip Smith wrote:
>>> On Oct 23, 2007, at 1:17 PM, David E. Wheeler
wrote:
>>>> On Oct 23, 2007, at 07:02, Phillip Smith
wrote:
>>>>> DBD::Pg::st execute failed: ERROR: 
duplicate key violates unique 
>>>>> constraint
"udx_output_channel_include"
>>>>> [for Statement "
>>>>>           INSERT INTO
output_channel_include (id, output_channel__id,
>>>>>                                        
      include_oc_id)
>>>>>          
VALUES(NEXTVAL('seq_output_channel_include'), ?, ?)
>>>>>       " with ParamValues:
2='1025', 1='1024'] at 
>>>>>
/home/domain/bricolage/lib/Bric/Util/DBI.pm line 1083,
<GEN1498> line 
>>>>> 1869.
>>>>> Please report this error to your
administrator.
>> 
>> Is it an upgraded system?
>
> Yes. From 1.10.2

I just looked at what udx_output_channel_include is,
and I don't think my question was relevant
(I was wondering if the sequence was reset.)

I don't know if it's worth worrying about
if it ended up working, and is no longer reproducible.

Is there an easy way to send an e-mail to all the users in
the  
system?  Do I need to create an alert?

Thanks,

Matt

On Oct 30, 2007, at 12:52, Matt Rolf wrote:

> Is there an easy way to send an e-mail to all the users
in the  
> system?  Do I need to create an alert?

Yeah, that would be the way to do it. Though making it so
that it  
happens only once for each user might be tricky…maybe tie it
to an  
action that only you can make, then make it, then delete the
alert type.

Best,

David