Easily manage the contents of your storage account with Azure Storage Explorer. Upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities. Gain easy access to manage your virtual machine disks. Work with either Azure Resource Manager or classic storage accounts, plus manage and configure cross-origin resource sharing (CORS) rules.
Creative Commons Attribution 4.0 International
365
stars
85
forks
source link
Persist column data independently for each blob container/file share/queue #7959
Column data for tables are preserved independently of each other. This is done primarily because tables have different columns.
Column data for blob containers, file shares, queues, etc. are preserved for all containers, shares, queues, etc. This is done primarily because they have the same set of columns.
However, it is likely that users may want to preserve different column data depending on the container. For example, auto-sized columns will differ from container to container depending on the data they contain (the Name column size will differ between containers). If preserved columns settings persist for all containers, an auto-sized column for one container would change the column size for all other containers, which would not be appropriate.
Column data for tables are preserved independently of each other. This is done primarily because tables have different columns.
Column data for blob containers, file shares, queues, etc. are preserved for all containers, shares, queues, etc. This is done primarily because they have the same set of columns.
However, it is likely that users may want to preserve different column data depending on the container. For example, auto-sized columns will differ from container to container depending on the data they contain (the Name column size will differ between containers). If preserved columns settings persist for all containers, an auto-sized column for one container would change the column size for all other containers, which would not be appropriate.