On 2009-04-28, David wrote:
> Ok got permission to send the code I think I have got all the relevent bits.
>
>CREATE TABLE currentcall (
>cadc_taskno integer DEFAULT
> nextval(('currentcall_cadc_taskno_seq'::text)::regclass) NOT NULL,
>coversight character varying(4),
...
>CREATE RUL
On 2009-04-28, David wrote:
> Our internal task database is doing something odd in that the sequence is
> incrementing by 2 instead of 1 and I can't find any reason why I have checked
> the
> sequence itself to see if it had somehow got set to increment by 2 but no.
> The table in question has
Cool thanks that makes sense was hard to pin down because we didn't notice for
a while.
On Tue, Apr 28, 2009 at 09:31:26AM +0200, Daniel Verite wrote:
> David wrote:
>
> >the sequence is incrementing by 2 instead of 1 and I can't
> >find any reason why I have checked the
> >sequence itsel
David wrote:
the sequence is incrementing by 2 instead of 1 and I can't
find any reason why I have checked the
sequence itself to see if it had somehow got set to increment
by 2 but no.
The table in question has a number of both before and after triggers
that do various bits of busines
Ok got permission to send the code I think I have got all the relevent bits.
On Tue, Apr 28, 2009 at 01:01:39AM -0600, Scott Marlowe wrote:
> On Tue, Apr 28, 2009 at 12:38 AM, David wrote:
> > Looked for that can't find anything and there is no reason why someone
> > would have added that.
>
>
On Tue, Apr 28, 2009 at 12:38 AM, David wrote:
> Looked for that can't find anything and there is no reason why someone would
> have added that.
Well, unless you've got some example code for us to look at, it's
kinda hard to tell you what's wrong.
Often, you see people do something like this:
Looked for that can't find anything and there is no reason why someone would
have added that.
On Tue, Apr 28, 2009 at 08:24:46AM +0200, A. Kretschmer wrote:
> In response to David :
> > Our internal task database is doing something odd in that the sequence is
> > incrementing by 2 instead of 1 a
In response to David :
> Our internal task database is doing something odd in that the sequence is
> incrementing by 2 instead of 1 and I can't find any reason why I have checked
> the
> sequence itself to see if it had somehow got set to increment by 2 but no.
> The table in question has a num
David, 28.04.2009 07:48:
Our internal task database is doing something odd in that the
sequence is incrementing by 2 instead of 1 and I can't find any
reason why I have checked the sequence itself to see if it had
somehow got set to increment by 2 but no. The table in question has a
number of bot
Our internal task database is doing something odd in that the sequence is
incrementing by 2 instead of 1 and I can't find any reason why I have checked
the
sequence itself to see if it had somehow got set to increment by 2 but no. The
table in question has a number of both before and after trig
10 matches
Mail list logo