The WITH that I am thinking about, lets you define and reuse queries which are executed once. For example:
WITH
MySummary AS (*SELECT b.dept_name, Sum(Salary) AS total_sal FROM emp a join dept b on (a.dept_id = b.dept_id)
GROUP BY b.dept_name*)
SELECT dept_name, total_sal //FROM
the import process to be done again.
I was under the impression that the nested transaction feature would
make this go away.
I played a little with it and it seems that the entire transaction is
aborted even if a checkpoint is
created.
Could someone please help me with this?
-Thanks,
Edwin S
Hello,
I have a much clearer picture of the issue. So, does this mean that
with nested transactions, all statements will execute within a
mini-transaction, which may be executed within a branch of user
defined sub-transactions. Such that:
begin
...
...
begin
...
...
Oh, yea, that would be bad. So you want to invalidate the entire
session on any error? That could be done.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
Well, that's exactly the current behaviour, which creates
Can we clarify what is meant by the client? It is my
expectation/desire that the client library would handle this as a
setting similar to AutoCommit, which would implicitly protect each
statement within a nested block (savepoint), causing only itself to
abort. Such as, OnError=[abort|continue],
Hello,
Is is possible to change the transaction behaviour not to abort when a
syntax error occurs.
I've done some searches on the list, and have not found anything.
-ESR-
---(end of broadcast)---
TIP 6: Have you searched our list archives?
Hello,
I need Postgres support for the following update syntax :
update table1 set (col1, col2, col3) = (select f1, f2, f3 from table2
where id=5) where rownum=3;
update table1 set (col1, col2, col3) = (select f1, f2, f3 from table2
where id=table1.parentid) where rownum=3;
These type of
Hello,
Are update statements like:
update t1 set (f1, f2, f3) = (select t1, t2, t3 from tab1 where id=5) where id=3
standard. Any hope of supporting this in Postgres?
-Edwin S. Ramirez-
---(end of broadcast)---
TIP 9: the planner will ignore
I tried :
select count('x') from patients;
And I get the same error.
select count('x'); should return the same as select count(*); which
returns 1.
Previous Postgres versions returned 1.
-ESR-
Peter Eisentraut wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Hello,
It appears that the count('x') will no longer work without a type
cast. Is this on purpose? I've already modified my code to use
count(*) instead, but I decided to mention it anyway.
warehouse=# select count('x') ;
ERROR: cannot accept a value of type any
warehouse=# select
Hello,
I would like to implement a function similar to the Decode function in
Oracle. I was wondering if it is possible to accept a variable number
of parameters (array??).
Thanks,
Edwin S. Ramirez
---(end of broadcast)---
TIP 5: Have you
11 matches
Mail list logo
