PostgreSQL-Select PostgreSQL-Lookup PostgreSQL-Execute | Table columns of the Array type now output the data as a list instead of a string. | Output as a string: {array_col_value={a, b, c}}
| Output message is now in an array: {array_col_value=[a, b, c]}
|
PostgreSQL-Delete PostgreSQL-Execute PostgreSQL-Insert PostgreSQL-Update | The various invalid SQL operation scenarios that result in failure include the following (but are not limited to): provided Where a column referenced in the query does not exist in the table.When you perform a delete operation that references a non-existent column. When you use an operator that does not exist or does not match given argument types. When the query references some relation (schema, table, etc.) that does not exist. When the query references a column that does not exist
| Error Message: SQL operation failed/core errors Reason: ERROR: invalid input syntax for type "DataType": "Invalid input" <scenario-specific message> Position: <number>, error <error code : 0, and SQL state information> For example: 22007 ERROR:
column\"query\"of relation \"updateTests\"does not exist\n \"query\" = 'id =2', \n \"id\" = 2,\n \"c_int\" = 40\nwhere (id=2) was aborted. Reason: "Error: column\"query\"of relation\"does not exist\n Position: 0, error code: 0, SQL state:42703",Error Message: Batch operation failed | Reason: Batch entry 0 <query> was aborted: ERROR: invalid input syntax for type 'Col DataType' : "invalid input" <scenario-specific message> Position: <number> Call getNextException to see other errors in the batch., error <error code : 0, and SQL state : 22007, next exception: ERROR: invalid input syntax for type 'Col DataType': "invalid input" Position: <number> ERROR: 42703, next exception: ERROR: column \"query\"of relation\"updateTests\" does not exist\n Positon: 40", Reason: "Batch entry 0 update\"snapteam1\".\"updateTests\"\nset\n \"query\" = 'id = 2',\n \"c_int\" = 40\nwhere (id = 2) was aborted: | Scenarios that can result in these kinds of error message changes include (but are not limited to): When the input value provided for a column is invalid for the column type. When performing a delete that references a non-existent column. When using an operator that does not exist or does not match given argument types. When the query references some relation (schema, table, etc.) that does not exist. When the query references a column that doesn’t exist
| Batch entry 0 <query> was abortedinformation>, next exception: ERROR: <scenario-specific message> Position: <number> Call getNextException to see other errors in the batch., <error code and SQL state info>, next exception: <>
|
PostgreSQL-Select | When the metadata is returned from the Snap’s second output view. | The original number of columns in the input data is displayed in the output. | In Select Snap, the second output view, some new columns are introduced.
For example, IS_GENERATEDCOLUMN , REF_GENERATION, SELF_REFERENCING_COL_NAME, TYPE_CAT, TYPE_NAME, TYPE_SCHEM |
PostgreSQL-Delete | When the delete condition has an unterminated quote string. | Error message: SQL operation failed
Reason : ERROR: unterminated quoted string at or near "' )"\n Position: <number>, error code: 0, SQL state: 42601
| Error message: SQL operation failed
Reason: "SQL [<query>]; Unterminated string literal started at position <number> in SQL <query>. Expected char"
|
All PostgreSQL Snaps | When the Dynamic Account has incorrect credentials. | Error : SQL operation failed
Reason : "java.lang.RuntimeException: Driver org.postgresql.Driver claims to not accept jdbcUrl, jdbc:postgresql://??postgresql-v10.nia.snaplogic.com:5432/snapteam?OpenSourceSubProtocolOverride=true, Driver org.postgresql.Driver claims to not accept jdbcUrl, jdbc:postgresql://??postgresql-v10.nia.snaplogic.com:5432/snapteam?OpenSourceSubProtocolOverride=true"
| Error message: SQL operation failed
Reason : "Failed to retrieve a database connection."
|
