U0530006: Default option behaviors defined for sequences are inconsistent between SQL Server and TaurusDB for PostgreSQL
Description
Database Type and Version
- Source database type and version: all SQL Server versions
- Target database type and version: TaurusDB for PostgreSQL 16.4 and later
Syntax Example
The default option behaviors (MINVALUE, MAXVALUE, START WITH) defined for sequences in SQL Server and TaurusDB for PostgreSQL may be different. For example:
SQL Server syntax:
CREATE SEQUENCE seq1
START WITH 1
INCREMENT BY 1
MAXVALUE 2
CYCLE
GO
-- 1 is returned for both SQL Server and TaurusDB for PostgreSQL.
SELECT NEXT VALUE FOR seq1
-- 2 is returned for both SQL Server and TaurusDB for PostgreSQL.
SELECT NEXT VALUE FOR seq1
-- For SQL Server, –9223372036854775808 is returned. For TaurusDB for PostgreSQL, 1 is returned.
SELECT NEXT VALUE FOR seq1
Suggestion
Ignore the related prompt or explicitly specify options such as MINVALUE, MAXVALUE, and START WITH as prompted.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot