| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
These text fields need a default of NULL aparently.
Signed-off-by: Malf Furious <m@lfurio.us>
|
|
I found myself complicating the data model of this class of objects and
wanted to take a clean approach to its design. The key differences are
as follows:
* We now reference a message object for the issue's OP, as
opposed to directly containing the message data
This affords the OP _all_ of the standard features of a Scrott
message, including separately tracked authorship data, file
attachments.
* Multiple assignees is implemented in the design
Finally.
* Seen flag is removed
This can be implicitly tracked via all sub-object messages and
the views meta-table.
|
|
|
|
|
|
|
|
This places all (both) of the service configuration files together and
cleans up the top-level directory. The file is renamed to 'mysql.sql'
to indicate the particular service it corresponds to.
|
|
I was experiencing problems on Mysql proper with the way Scrott
interacts with the database when forming new objects. It attempts some
writeback querries before all attributes are applied to the new objects.
This makes sense if you understand how many initNew and helper functions
are implemented. As a convenience a function which mutates an object
will also apply its changes to the database automatically. These
function are used instead of directly settings PHP object properties
because there are additional pieces of logic performed to ensure
everything remains valid in the datamodel.
As was the case for a few types of objects, cirtain functions which
behave this way were being called during an object's initNew(), causing
DB writebacks to occur before some other 'default-less' field had been
defined for that object.
This patch provides some 'not so invalid' default states for database
table columns which were previously undefined. This should also
mitigate some issues I may have not run unto yet.
|
|
I don't mean to impose a character limit here, so I am changing this
type to 'text'. As per the previous commit, the default value is also
removed.
|
|
It is an error in Mysql for columns of type 'text' to have a default
value. Removing these resolves Mysql errors and MariaDB warnings.
|
|
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.
|
|
|
|
|
|
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
|
