ms to be outdated. As far as I know it was supposed to warn for
the HyperThreading things.
- --
Viele Grüße,
Lars Heidieker
[EMAIL PROTECTED]
http://paradoxon.info
-
Mystische Erklärungen.
Die mystischen Erklärungen gelten für tief;
die Wahrheit ist, das
-lpq
--
Viele Grüße,
Lars Heidieker
[EMAIL PROTECTED]
http://paradoxon.info
Mystische Erklärungen.
Die mystischen Erklärungen gelten für tief;
die Wahrheit ist, dass sie noch nicht einmal oberflächlich sind.
-- Friedrich Nietzsche
PGP.sig
Descrip
ething ?
- --
Viele Grüße,
Lars Heidieker
[EMAIL PROTECTED]
http://paradoxon.info
-
Mystische Erklärungen.
Die mystischen Erklärungen gelten für tief;
die Wahrheit ist, dass sie noch nicht einmal oberflächlich sind.
-- Friedrich Nietzsche
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28 Nov 2006, at 13:33, Olexandr Melnyk wrote:
Looks like I've missed your mail, so a late reply.
2006/11/11, Lars Heidieker <[EMAIL PROTECTED]>:
> > > While I agree in principle that such a thing should be
> > &g
rialized
path eg for the values (25, 25)
It works OK with ignoring the exception but why is the exception
thrown in the first place.
The postgresql version 8.1.5
- --
Viele Grüße,
Lars Heidieker
[EMAIL PROTECTED]
http://paradoxon.info
-
Mystische Erkl
g Alban Hertroys suggested to get an
better understanding of what is going on.
- --
Viele Grüße,
Lars Heidieker
[EMAIL PROTECTED]
http://paradoxon.info
-
Mystische Erklärungen.
Die mystischen Erklärungen gelten für tief;
die Wahrheit ist, dass sie noch n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18 Dec 2006, at 09:37, Alban Hertroys wrote:
Lars Heidieker wrote:
Hi all,
I just started to write my first stored procedure in plpgsql and
installed a trigger for it.
The two Tables are:
CREATE TABLE ltlocation (
"id" integ
key constraint.
So it makes sense to rewrite the trigger to take only care of those
cases that aren't handled by the cascading foreign keys.
- --
Viele Grüße,
Lars Heidieker
[EMAIL PROTECTED]
http://paradoxon.info
-
Mystische Erklärungen.
Die mys
erstanding.
Thanks, yes the ltlocancester_id is invalid as it was changed by the
foreign key constraint before,
in the end it turned out to be some bad interaction between the
trigger and the foreign key constraint,
as Albe Laurenz found out.
That's where I got confused.
(Yes, u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 10:30, Lars Heidieker wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 08:56, Alban Hertroys wrote:
Not sure as I deleted them before, but currently I cant reproduce
it.
I just get the following
h (ltlocation_id, ltlocancester_id)
VALUES (new.id, workid);
SELECT INTO workid parent FROM ltlocation WHERE id =
workid;
END LOOP;
END IF;
RETURN new;
END;
$$ LANGUAGE plpgsql;
So it handles only the cases the foreign keys can't an
ituation is a transaction that
touches the rows in a transaction and
keeps the transaction alive before vacuum runs.
- --
Viele Grüße,
Lars Heidieker
[EMAIL PROTECTED]
http://paradoxon.info
-
Mystische Erklärungen:
Die mystischen Erklärungen gelten für tie
12 matches
Mail list logo