id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
1958,Brittle queries,bewst,bobbysmith007,I have some ticket_change entries with a blank newvalue field:\r\n{{{\r\ntrac=# select author_ oldvalue_ newvalue from ticket_change where field = 'hours';\r\n author  | oldvalue | newvalue\r\n---------+----------+----------\r\n gargol  |          | 12\r\n gargol  |          | 8\r\n gargol  |          | 2\r\n gargol  |          |\r\n gargol  |          |\r\n gargol  |          |\r\n gargol  |          |\r\n gargol  | 0        | 4\r\n gargol  | 0        | 7\r\n gargol  | 0        | 1\r\n gargol  | 0        | 4\r\n gargol  |          | 4\r\n gargol  | 0        | 3\r\n gargol  | 0        | 5\r\n gargol  | 0        | 2\r\n towerx  | 0        | 9\r\n pcaster | 0        | 16\r\n(17 rows)\r\n}}}\r\n\r\nThis is causing all the queries to break on {{{CAST(newvalue as DECIMAL)}}} (PostgreSQL):\r\n\r\n{{{\r\nERROR:  invalid input syntax for type numeric: ""\r\n}}}\r\n\r\nThe simplest workaround I could find was to use  {{{CAST(('0'||newvalue) as DECIMAL)}}} instead.  I'm hardly an SQL expert_ though.,defect,closed,normal,TimingAndEstimationPlugin,major,fixed,,,0.11