Datapackfiles Model

Overview

The datapackfiles table stores metadata about files associated with different data packs. These files could be configuration files, scripts, or other supporting documents that are part of a data pack.

Fields

Field	Type	Description	Required
id	string	Primary Key – Unique identifier for each file (UUID).	❌
name	string	The Name of the file. Usually includes file extension (e.g., init.sql, report.json).	✅
size	number	Stores the file size, though storing as text may not be ideal.	❌
path	string	The file's storage location or relative path.	✅
documentId	any	Reference to an associated document (if applicable).	❌
statusType	any	Describes the file’s state ex: generated, uploaded, archived, pending.	❌
creationType	string	Indicates how the file was created, e.g., manual, automated, scripted, imported.	✅
fileSource	string	Source of the file (e.g., uploaded, generated).	❌
internalPublished	boolean	Boolean flag (0/1) indicating if the file has been published internally.	❌
isScriptFile	boolean	Boolean flag indicating if the file is a script (e.g., SQL, Python). Useful for automation.	❌
active	string	Boolean flag indicates whether the file is currently in active use.	✅
created_at	date	Timestamp when the file entry was created.	❌
modified_at	date	Timestamp when the file entry was last modified.Useful for version tracking.	❌
datapackId	string	Foreign key reference to the datapackbuilds or datapacks table	✅

Relationships

• Belongsto Unknown
• Belongsto Unknown

Sample JSON

{
  "id": "example_value",
  "name": "example_value",
  "size": "example_value",
  "path": "example_value",
  "documentId": "example_value",
  "statusType": "example_value",
  "creationType": "example_value",
  "fileSource": "example_value",
  "internalPublished": "example_value",
  "isScriptFile": "example_value",
  "active": "example_value",
  "created_at": "example_value",
  "modified_at": "example_value",
  "datapackId": "example_value"
}