You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SQL produced for any table with an identity column will be invalid.
[1] fake.fake.1> sp_help TestProducer;
Name Owner Object_type Object_status Create_date
------------------------ ---------- ---------------------- -------------------------- --------------------------------------
TestProducer dbo user table -- none -- Jul 13 2017 12:42PM
(1 row affected)
Column_name Type Length Prec Scale Nulls Not_compressed Default_name Rule_name Access_Rule_name Computed_Column_object Identity
---------------------- -------------- ------------ -------- ---------- ---------- ---------------------------- ------------------------ ------------------ -------------------------------- -------------------------------------------- --------------------
TestID numeric 5 9 0 0 0 NULL NULL NULL NULL 1
TestVar varchar 2 NULL NULL 0 0 NULL NULL NULL NULL 0
TestChr char 1 NULL NULL 1 0 NULL NULL NULL NULL 0
Object does not have any indexes.
No defined keys for this object.
If I have SQL::Translator::Producer::Sybase dump out the SQL for this table then I get this (comments and blank lines removed):
CREATE TABLE TestProducer (
TestID IDENTITY numeric(9,0) NOT NULL,
TestVar varchar(2) NOT NULL,
TestChr char(1) NULL
);
Notice that IDENTITY falls before the datatype which is invalid, will not load in Sybase and rightly causes SQL::Translator::Parser::Sybase to error out.
The text was updated successfully, but these errors were encountered:
The SQL produced for any table with an identity column will be invalid.
If I have SQL::Translator::Producer::Sybase dump out the SQL for this table then I get this (comments and blank lines removed):
Notice that IDENTITY falls before the datatype which is invalid, will not load in Sybase and rightly causes SQL::Translator::Parser::Sybase to error out.
The text was updated successfully, but these errors were encountered: