I format query to read it more easy. See attachment
Tuesday, December 8, 2020, 3:43:13 PM, you wrote:
Hello Tom,
>>> Also would be useful if PG point at query where this bad value was
>>> calculated or occur.
>> This is not the first time we've seen this request and it usually ends up
>> getti
Hello Tom,
>>> Also would be useful if PG point at query where this bad value was
>>> calculated or occur.
>> This is not the first time we've seen this request and it usually ends up
>> getting stalled because its non-trivial to implement and thus isn't
>> feasible for the benefit it brings.
>
"David G. Johnston" writes:
> On Sat, Nov 28, 2020 at 4:18 PM Eugen Konkov wrote:
>> I often fall into error like this:
>> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st
>> execute failed: ERROR: timestamp out of range
>> Would be nice if here also will be reported error v
On Sat, Nov 28, 2020 at 4:18 PM Eugen Konkov wrote:
> Hi all.
>
> I often fall into error like this:
>
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st
> execute failed: ERROR: timestamp out of range
> CONTEXT: SQL function "accounting_ready" statement 1 [for Statement
>
Hi all.
I often fall into error like this:
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute
failed: ERROR: timestamp out of range
CONTEXT: SQL function "accounting_ready" statement 1 [for Statement "SELECT
COUNT( * ) FROM (WITH
target_date AS ( SELECT ?::timestamp
