Some places in UnityDataTool, including the analyze schema use "AssetBundle" when the functionality is actually general to any use of the Unity Archive file format.
Primarily the name of this table is potentially misleading:
CREATE TABLE IF NOT EXISTS asset_bundles
(
id INTEGER,
name TEXT,
file_size INTEGER,
PRIMARY KEY (id)
);
Unity uses archive files also for player builds and "content archives". Having very clear terminology will help everyone understand the file formats, especially as we introduce new build functionality that doesn't involve AsssetBundles.
Changing the core Analyze schema could have an impact on some existing tools (they may have to do some search and replace to fix table names in queries). I think its still in the best interest of everyone to keep the schema improving.
This will be included along with a clear bump in the version (e.g. 1.3.X -> 2.0) so that this doesn't suddenly appear in a point bug fix release.
And the mapping of any renamed database content should be clearly listed in the release notes.
Some places in UnityDataTool, including the analyze schema use "AssetBundle" when the functionality is actually general to any use of the Unity Archive file format.
Primarily the name of this table is potentially misleading:
Unity uses archive files also for player builds and "content archives". Having very clear terminology will help everyone understand the file formats, especially as we introduce new build functionality that doesn't involve AsssetBundles.
Changing the core Analyze schema could have an impact on some existing tools (they may have to do some search and replace to fix table names in queries). I think its still in the best interest of everyone to keep the schema improving.
This will be included along with a clear bump in the version (e.g. 1.3.X -> 2.0) so that this doesn't suddenly appear in a point bug fix release.
And the mapping of any renamed database content should be clearly listed in the release notes.