Project

General

Profile

Actions

Testing #2797

closed

[PostgreSQL]: Invalid input syntax for type integer in redmine_computable_custom_field

Added by liaham 3 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
01/08/2025
Due date:
01/09/2025
% Done:

100%

Estimated time:
Compatible Redmine Version:
5.1.z

Description

  1) Error:
ComputableCustomField::EnumerationFormatPatchTest#test_should_sort_numerically:
Query::StatementInvalid: PG::InvalidTextRepresentation: ERROR:  invalid input syntax for type integer: "12.0"

    app/models/issue_query.rb:424:in `rescue in issues'
    app/models/issue_query.rb:380:in `issues'
    plugins/redmine_computable_custom_field/test/unit/lib/overrides/enumeration_format_patch_test.rb:108:in `block in <class:EnumerationFormatPatchTest>'

Related issues 1 (0 open1 closed)

Related to Redmine Matrix Field - Improvement #2803: Change casting to integer for postgresql to avoid invalid input syntax errorsClosedliaham01/10/202501/10/2025

Actions
Actions #1

Updated by liaham 3 months ago

  • Assignee set to liaham
Actions #2

Updated by liaham 3 months ago

  • Project changed from xmera Omnia to Redmine Computable Custom Field
  • Status changed from New to In Progress
  • Target version changed from 4.3.1 to 3.1.0
  • % Done changed from 0 to 50
Actions #3

Updated by liaham 3 months ago

  • Due date set to 01/09/2025
  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100
Actions #4

Updated by liaham 3 months ago

Postgresql requires a different casting to integer than sqlite.

Actions #5

Updated by liaham 3 months ago

  • Related to Improvement #2803: Change casting to integer for postgresql to avoid invalid input syntax errors added
Actions

Also available in: Atom PDF