remco lengers wrote:
Hi List,
Its been a while since I worked with databases and I am running into the
following which I have not been able to find the root cause for:
I have the follow SQL statement:
INSERT INTO reference VALUES (DEFAULT,'123','2',1);
Which generates the following error:
"E
Use
INSERT INTO reference(reference_text, reference_type, Topic_Id) VALUES
(DEFAULT,'123','2',1);
instead.
Since referencelist_nr is a serial PostgreSQL will provide the next free
integer itself.
>>> "remco lengers" <[EMAIL PROTECTED]> 2007-03-20 10:11 >>>
Hi List,
Its been a while since I wo
Hi List,
Its been a while since I worked with databases and I am running into the
following which I have not been able to find the root cause for:
I have the follow SQL statement:
INSERT INTO reference VALUES (DEFAULT,'123','2',1);
Which generates the following error:
"ERROR: duplicate key v
The problem is solved. It is a silly mistake actually. The line
SELECT sid FROM conf_category WHERE
category_name like temp_category and category_status=1;
returns duplicated values. Variable temp_category would be '%dos.rules'
and there are entries 'dos.rules' and 'ddos.rules' in t
Khairul,
> Need help on this problem. I've created two functions. The function
> should perform a few sql processes. The problem is I got different
> results when I call the function and when I manually run the sql command.
>
> I'm using postgresql 7.4.2.
Hmmm ... that's odd. I remember getting
Need help on this problem. I've created two functions. The function
should perform a few sql processes. The problem is I got different
results when I call the function and when I manually run the sql command.
I'm using postgresql 7.4.2.
The two functions involved are
CREATE TABLE sensor_signatur
