Hi Magnus,
thanks for the answer.
On Mon, 1 Nov 2004 12:24:07 +0100, you wrote:
>
>Not sure if we want to add a workaround for that? It'd be needed for
>every single command, so I personally don't think it's a good idea.
>
Maybe discarding semicolons in database's names passing the command to
ve a db name ending with semicolon. This is
not a problem really, but this happens only in this version/platform.
Thanks you all guys.
Regards,
Silvio Scarpati
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
er of copies equal to the number of duplicates.
Right ! i forgot that :-) (blushing).
Sorry.
Thank you again,
Silvio Scarpati
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
e query should return 4 rows. In other words i don't know
why postgres performs the following query:
select a,b from t1 union (select DISTINCT a,b from t2);
instead of the required one.
I think i's a bug.
Thank you.
Silvio Scarpati
---(end of broadcast)
e
precision as '
select cast(round(cast($1 as numeric),$2) as double precision);
' LANGUAGE SQL with(iscachable) ;
I hope this can help someone.
Regards,
Silvio S
