-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mssql: table partition support #3266
Comments
Hello, can you please share the SQL that create the table? |
Sorry, also the create schema script. I need the sql to preproduce the issue |
`CREATE PARTITION FUNCTION pfLog AS RANGE RIGHT FOR VALUES (20220101, 99999999) CREATE TABLE [test].[exec_log]( |
Hello @AnielaN994, we will exclude the partitioned tables from inspect result. In the meanwhile, please use the exclude flag to ignore this table. |
Hello. It's not only this tables, we have more tables like this and we want their definition to be in the generated schema.sql via inspect in order to execute the script on other databases and for the moment we can exclude the partition schemes until they will be supported but we cannot exclude the tables themselves. |
Hello,
We have tables partitioned by scheme that I've understood they'll be supported by atlas in feature releases and for some of those partitioned by scheme tables, there is no Primary key created. Hence there is a default heap entry in sys.indexes that has the name NULL.
Due to this, at atlas schema inspect, "Error: mssql: sql: Scan error on column index 2, name "index_name": converting NULL to string is unsupported" is returned. When I create myself the PK on the table, the error is no more encountered.
When the migration is done with flyway, the error is not encountered from the default heap entry in sys.indexes.
Is there any solution for this ?
Many Thanks.
The text was updated successfully, but these errors were encountered: