René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Populate Type table during BuildReport import","articleBody":"Follow up to #47 \n\nBuildReport files record types using the type ID, not the string name.  That is good for saving diskspace and computations but its not human friendly when viewing the report data in the analyze database.\n\nThe Analyze schema has a \"types\" table that can be used to map from id to string, this is useful to JOIN against for views and other queries so that the human friendly type is shown.\n\nIn #47 we introduce a hard coded list of those types (for use when we don't have the string), and more recently in 0c36a907a41e2f960b57d7f147237c0d0e91d137 this list was made comprehensive (so that we could use it reliably for the type argument to the dump command).\n\nThis task is to use _UnityFileSystem/TypeIdRegistry.cs_ in _Analyzer/SQLite/Handlers/PackedAssetsHandler.cs_ and dynamically populate the type table if the type is not already present.\n\nOnce this is done we can update `build_report_packed_asset_contents_view` to show the string-based type, instead of the numeric value, making it a lot easier to understand.\n\n\n\n","author":{"url":"https://github.com/SkowronskiAndrew","@type":"Person","name":"SkowronskiAndrew"},"datePublished":"2025-12-31T21:38:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/55/UnityDataTools/issues/55"}