Issues and Troubleshooting
In this section, you will find information about Errors, Warnings, and Issues on the SnowConvert.
This is a deprecated version of the SnowConvert documentation, please visit the official site HERE.
Conversions of any large quantity of code will likely have a few errors and warnings. When using any of our tools, you can count on us to be your partner in resolving any errors you may encounter.
Below is a list of specific conversion issues for PostgreSQL that you may see when you perform a conversion with SnowConvert along with a severity level for each. Some suggested solution paths based on the severity level will follow the list of codes.
Take a minute to read through the list and the troubleshooting tips to help diagnose some of the error codes you have encountered. If you have a question that cannot be answered here, please reach out! You can drop us an email at snowconvert-support@snowflake.com. This is a living list, so it will grow and change as SnowConvert evolves. Updates to issue and error handling will appear on this page.
Issues Code
Here is the list of error codes that SnowConvert might generate for PostgreSQL conversions. A description of the severity levels and some troubleshooting suggestions will follow this list of codes.
| Code | Description | Severity |
|---|---|---|
User privileges must be handled manually. | Low | |
Age not supported | Medium | |
Bpchar converted to varchar | Low | |
Bytea Converted To Binary | Low | |
The date output format may vary | Low | |
Set search path with multiple schemas | Medium | |
Raise notice translated to user-defined stored procedure. | Low | |
Constraint index parameter not supported | Low | |
Inheritance not supported | Low | |
Exclude constraint not supported | Medium | |
Precision format is not supported in Snowflake. | Medium | |
The current to_char date format may have a different behavior in Snowflake. | Low | |
The current to_char numeric format may fail or have a different behavior in Snowflake. | Medium | |
Unsupported Raise Exception. | Medium | |
Raise Exception translated to user-defined stored procedure call and raise stat. | Low | |
The current Timestamp format may have a different behavior in Snowflake. | Low | |
The lock level is handled automatically in Snowflake. | Low | |
Select with Into clause is not compatible with snowflake, it is transformed to a Create Table As. | Low | |
Select with Into clause is not compatible with snowflake, it is transformed. | Low | |
The use of Invertal within a to_char function is not compatible with Snowflake. | High | |
Comment on 'Type' is not supported by Snowflake. | Low | |
NULL is converted to '' and may have a different behavior in Snowflake. | Low | |
Materialized view is only supported in the enterprise version of Snowflake. | Low | |
The argument mode (IN, OUT, INOUT, VARIADIC) are not supported by Snowflake. By default, all the arguments are in IN mode. | Low | |
Advance sequence and return new value. | Low | |
Sequence 'TEMPORARY | Temp' is not supported by Snowflake. | Low | |
The sequence option 'option_name' is not supported by Snowflake. | Low | |
FOUND could have a different behavior in Snowflake in some scenarios. | Low | |
TRUNCATE RESTRICT BEHAVIOR SHOULD BE USED WHEN NOT HAS REFERENCES | Low |
Issues Severity
In this section, you can find an explanation of the severities.
Low
Warnings for source code that there was no direct conversion to Snowflake. The code has been converted to a functional equivalent output but should still be reviewed.
Medium
Errors that produce a functional or runtime difference. The user may have to invest a low amount of manual effort to complete the conversion.
High
Errors that produce a functional or runtime difference. The user may have to invest a high amount of manual effort to complete the conversion.
Critical
Parsing errors or errors that cause significant conversion exceptions in SnowConvert. If the source code is correct, significant intervention will be required.
Last updated