Table Definition - Standard
Submitted by Synthetic Dreams on Fri, 08/15/2014 - 15:17
| Field | Type | Read-only | Description |
|---|---|---|---|
| ID | Integer | Yes | Primary Key (unique ID) for row |
| Path | Char | No | Full pathname. Must be specified for INSERT statements. Will normally rename/move file when used in UPDATE statements, or copy the file when copy mode is enabled |
| Parent | Char | No | Parent directory. Will normally move file when used in UPDATE statements, or copy the file when copy mode is enabled |
| Name | Char | No | Filename. Will normally rename file when used in UPDATE statements, or copy the file when copy mode is enabled |
| Base | Char | No | Filename without extension. Will normally rename file when used in UPDATE statements, or copy the file when copy mode is enabled |
| Extension | Char | No | File extension (include leading dot). Will normally rename file when used in UPDATE statements, or copy the file when copy mode is enabled |
| Size | Integer | Yes | Filesize in bytes |
| CreateDate | Timestamp | No | File creation date/time |
| ModifyDate | Timestamp | No | File last modified date/time |
| Directory | Integer | Yes* | 0 = File, 1 = Directory. *Must be specified for INSERT statements to create directories |
| ReadOnly | Integer | No | File Attribute: Read-only (0 = No, 1 = Yes) |
| Hidden | Integer | No | File Attribute: Hidden (0 = No, 1 = Yes) |
| System | Integer | No | File Attribute: System (0 = No, 1 = Yes) |
| Archive | Integer | No | File Attribute: Archive (0 = No, 1 = Yes) |
| Compressed | Integer | Yes | File Attribute: Compressed (0 = No, 1 = Yes) |
Usage Notes
- INSERT and DELETE statements run against the 'Standard' table will create and delete files/directories, respectively
- As noted, the 'Path' and 'Directory' fields must be specified, at minimum, for INSERT statements. Any non read-only field may also be specified in INSERT statements to be applied to newly created files/directories
- Changes made to fields will automatically reflect (upon the next query) to fields which contain aggregate information - e.g. if an UPDATE statement changes the 'Extension' column of a row, the 'Path' and 'Name' columns of that row will automatically reflect these changes in the next query run (and vice versa - changes to 'Name' would automatically reflect in 'Extension')
