Forest Wilkinson wrote:
>
> I'm having a problem with functions written in SQL. Specifically, they
> don't seem to be adhering to Postgres locking rules. For the record, I'm
> using postgres 7.0.2, installed from RPMs, on Red Hat 6.2.
>
> Here's what I'm seeing:
> (psql input represented by '<<
Meszaros Attila <[EMAIL PROTECTED]> writes:
> How far is the above subject from beeing implemented?
I'm looking at it right now ... no promises yet, though.
regards, tom lane
Forest Wilkinson <[EMAIL PROTECTED]> writes:
> session2<< select nextid('myid');
> (session2 blocks until session1 completes its transaction)
> session1<< commit;
session1> COMMIT
> (session2 resumes)
session2> nextid
session2>
session2> 0
session2> (1 row)
> What gives??? I expecte
Hi, there,
only possible is null, so select blah from tableblah where field is
null;
Jeff MacDonald wrote:
how would i select all rows where a boolean value
is neither
t nor f.. ?
ie if someone inserted without setting the boolean tag.
Jeff MacDonald,
-
I'm having a problem with functions written in SQL. Specifically, they
don't seem to be adhering to Postgres locking rules. For the record, I'm
using postgres 7.0.2, installed from RPMs, on Red Hat 6.2.
Here's what I'm seeing:
(psql input represented by '<<'; output represented by '>>'.)
sess
Hi All,
My question for this week:
How far is the above subject from beeing implemented?
(I've run through the archives, and found some quite old mails in
this topic. They mentioned automatically generated temp tables as possibe
solutions... Is this the plan even today?)
Attila
Ps.:
Two weeks
