| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Defaulting this field to the empty string since, by default, messages do
not have attachments.
|
|
Renamed from 'message' to 'mesg', for consistency with other naming
conventions.
|
|
Since the df.php script can detect the mime-type of files on disk, I am
removing this state from the database. With 'attachName' being the only
remaining field pertaining to attachments, I have simply renamed it
'attachment'.
|
|
To address potential bugs in the application code, I have updated the data
definition to forbid NULL values anywhere in the Scrott database.
Additionally, the data type for issue due datetimes is updated to
varchar since 'datetime' has issues with my desired default value.
|
|
|
|
|
|
'desc' is a SQL reserved word, changing this column name to
'description'.
|
|
|
|
Biggest changes include:
better comments
merged user and extern-user tables
separate fields for different permissions (not a bitmask)
added fields to mesgs table for handling attachments
renamed some fields to avoid using SQL reserved words
|
|
Setup to perform an iteration of development focused on a simpler
implementation and eliminating redundancy in design.
|
|
|
|
|
|
This adds attributes to an issue:
due date (optional datetime)
tags (space separated string of words to help categorize issues (again, optional))
|
|
Eliminate redunancy in the data model by using just one object type to denote 'log' instead of parent object specfic types (eg: log-user, log-group, log-pad, ....).
This is a redundancy because the type of the parent can be quired simply by following the log entry's parent ptr and assessing its type value.
|
|
When user objects are initially created they need to hold a NULL owner value (since users are self-owning objects and prior to db insertion their own guid is not known).
Also, the timeUpdated field will no longer hold special meaning for user objects and is now going to be treated as consistent with the rest of the data model.
|
|
User accounts now have a field to denote whether they are site administrators. The first account created during app initial configuration is an admin automatically.
|
|
|
|
value can now be user-specific
|
|
Message-type objects
|
|
|
|
|
|
|
|
|
|
|
|
|
|
objects (and their common attributes). Additional, supplemental tables may be employed to maintain data attributes which are specific to a given object type
|
|
|
|
|
|
|
|
! Devised an initial concept for Scrott object permissions system
|
