New to Postgres and I have never seen this condition. We are getting test
applications hanging on SELECT statements with a RowExclusiveLock. How can
a SELECT cause a RowExclusiveLock?
relname | pid | mode | granted
I am getting division by zero on a calculated field ( sum(sales) is 0 )
and I can't find a way around this. I figured out you can't use an
aggregate in a where, and using having the parser must (obviously)
evaluate the select fields before considering teh having clause.
Does anyone have a
We do the following test on the
client site :
A)Using SQLExecDirect with this query
SELECT SUM("str_sls_totals"."strsl_net_dly"),
"dw_trans_type"."trans_type", "flash_dates"."year_number",
"flash_dates"."month_number", "flash_dates"."day"
FROM "dw_trans_type", "str_sls_totals",
The column is decimal(16,2). Thanks.
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
