VbzCart/docs/tables/fm folder: Difference between revisions
Jump to navigation
Jump to search
imported>Woozle (Created page with '==About== * '''Purpose''': Stores complete information about where files are found and how they can be accessed; sort of a mini-FileFerret. * '''History''': ** '''2010-11-15'…') |
imported>Woozle (Spec -> PathPart) |
||
| Line 3: | Line 3: | ||
* '''History''': | * '''History''': | ||
** '''2010-11-15''' Created in order to deal with the fact that we're going to have more than one base URL for images (so we can upload new images to the wiki -- or whatever image server is handy -- and access them directly from there). | ** '''2010-11-15''' Created in order to deal with the fact that we're going to have more than one base URL for images (so we can upload new images to the wiki -- or whatever image server is handy -- and access them directly from there). | ||
** '''2010-11-16''' Decided to rename Spec to PathPart for coding clarity. | |||
* '''Future''': | * '''Future''': | ||
** This table only manages paths for one particular access method, i.e. the web (and only for read-only access). In the future we might have another table which gives methods for modifying (moving, renaming, adding, deleting) files. Ideally different methods would be consolidated into one more general-purpose table, but this is a task-specific table, so we're not going to do that. Maybe that functionality will be handled by [[FileFerret]], and this app will simply provide links to integrate with that. | ** This table only manages paths for one particular access method, i.e. the web (and only for read-only access). In the future we might have another table which gives methods for modifying (moving, renaming, adding, deleting) files. Ideally different methods would be consolidated into one more general-purpose table, but this is a task-specific table, so we're not going to do that. Maybe that functionality will be handled by [[FileFerret]], and this app will simply provide links to integrate with that. | ||
| Line 9: | Line 10: | ||
ID INT NOT NULL AUTO_INCREMENT, | ID INT NOT NULL AUTO_INCREMENT, | ||
ID_Parent INT DEFAULT NULL COMMENT "base for this spec", | ID_Parent INT DEFAULT NULL COMMENT "base for this spec", | ||
PathPart VARCHAR(255) NOT NULL COMMENT "relative filespec - the part of the path from parent to this file/folder", | |||
Descr VARCHAR(255) DEFAULT NULL COMMENT "brief name or description, for choice lists", | Descr VARCHAR(255) DEFAULT NULL COMMENT "brief name or description, for choice lists", | ||
PRIMARY KEY(`ID`) | PRIMARY KEY(`ID`) | ||
) ENGINE = MYISAM;</mysql> | ) ENGINE = MYISAM;</mysql> | ||
<section end=sql /> | <section end=sql /> | ||
Revision as of 12:44, 16 November 2010
About
- Purpose: Stores complete information about where files are found and how they can be accessed; sort of a mini-FileFerret.
- History:
- 2010-11-15 Created in order to deal with the fact that we're going to have more than one base URL for images (so we can upload new images to the wiki -- or whatever image server is handy -- and access them directly from there).
- 2010-11-16 Decided to rename Spec to PathPart for coding clarity.
- Future:
- This table only manages paths for one particular access method, i.e. the web (and only for read-only access). In the future we might have another table which gives methods for modifying (moving, renaming, adding, deleting) files. Ideally different methods would be consolidated into one more general-purpose table, but this is a task-specific table, so we're not going to do that. Maybe that functionality will be handled by FileFerret, and this app will simply provide links to integrate with that.
SQL
<section begin=sql /><mysql> CREATE TABLE `cat_folders` (
ID INT NOT NULL AUTO_INCREMENT, ID_Parent INT DEFAULT NULL COMMENT "base for this spec", PathPart VARCHAR(255) NOT NULL COMMENT "relative filespec - the part of the path from parent to this file/folder", Descr VARCHAR(255) DEFAULT NULL COMMENT "brief name or description, for choice lists", PRIMARY KEY(`ID`)
) ENGINE = MYISAM;</mysql> <section end=sql />