Forum Discussion
Advocate IIICreating a table in Fabric Warehouse - allow NULL values
Hi webchris ,
Thanks for the information. Apologies for the issue you are facing. Currently there is no bug for this feature. We can certainly keep an eye on it for upvote.Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Advocate IIIAnonymous
Good morning, thanks for your investigation.
When you now click on the three dots next to your table and select "Create", does the DDL Code show the correct types (esp. regarding nulls)? On my end, the "create"-statement resets all columns to "Not Null".
Thanks again
Christian
Hi webchris ,
Yes you are right, the create statement resets all the columns to "NOT NULL". But I couldnt understand why to create another table?
As per your ask, you stated that NULL columns are not inserted into the table. But when I created the table, I was able to insert NULL values.
If you are trying to create another table with same columns the editor resets the columns to "NOT NULL". Then you cannot insert NULL values into such table.
Could you explain me your ask more clearly, so that I can help you better?
Thank you.
- webchris
Anonymous
I know that, once created, the columns work and the NULL setting. But, we are in a process of developping our environment, which sometimes makes it necessary to re-create a table when the first version did not work - and e.g. more columns need to be Nullable.
When this happens, I can not just change this one column, but instead I always have to re-do the whole work for all columns - in tables with 120 columns that's a complex task.
Hi webchris ,
Thanks for the information. Apologies for the issue you are facing. Currently there is no bug for this feature. We can certainly keep an eye on it for upvote.Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Hi webchris ,
We haven’t heard from you on the last response and was just checking back to see if your issue has been resolved. Please let us know if you have any further queries.