Hi, this query gives different strange results:
select to_char(now()::abstime,'YYMMDDHH24MI');
I get e.g. a "backend closed the channel unexpectedly..." error with
successful or failed resetting attempt (indeterministic)
or
ERROR: to_char/to_number(): not unique decimal poit
or
NOTICE: Por
I'm not sure if this is a reported bug or not. SELECT statements with some
aggregates on certain complex views can give terrible results. An example:
CREATE TABLE master (
id int4 not null,
no int4 check (no >= 0) default 0,
primary key (id, no),
started date check ((not started i
Hi,
in fact this is a resent bug report. The Windows ODBC driver doesn't
detect that a reference integrity violation occured. It realizes the
fact that there was an error, but doesn't abort the transaction.
I didn't found SC_log_error (in SC_execute) being executed. IMHO it should
abort the tran
