eliseuamaro/gnu-social
1
0
Fork 0
forked from GNUsocial/gnu-social
Code Issues Pull Requests Releases Wiki Activity
19,066 Commits 8 Branches 3 Tags 310 MiB
b27bda6a7c
Commit Graph

12 Commits

Author SHA1 Message Date
Hugo Sales
460712e15e
[GIT] Change my email to the new one in all files and bump copyright year 2021-09-14 13:06:56 +01:00
Hugo Sales
c8e8f1f057
[ENTITY] Add Entity base class to all entities 2021-09-14 13:05:56 +01:00
Hugo Sales
51a1a1180e
[AUTOGENERATED] Update autogenerated code 2021-09-14 13:05:54 +01:00
Hugo Sales
1111ee95f1
[CORE] Data Representation and Modelling refactor 2021-09-14 13:05:53 +01:00
Hugo Sales
699f25a397
[AUTOGENERATED] Update autogenerated code 2021-09-14 13:05:51 +01:00
Hugo Sales
c7dbae8067
[AUTOGENERATED] Update autogenerated code 2021-09-14 13:05:49 +01:00
Hugo Sales
fe3a3978af
[UI][CONTROLLER] Work on tabbed notification settings panel 2021-09-14 13:05:46 +01:00
Hugo Sales
5b578b9519
[DATABASE] Fix typos in user_notification_prefs 2021-09-14 13:05:42 +01:00
Hugo Sales
2796ac5228
[NOTIFICATION][DATABASE] Update user notification prefs table, implementation of Notification and define a base class for notification transport 2021-09-14 13:05:40 +01:00
Hugo Sales
97b583aee7
[AUTOGENERATED] Update autogenerated code 2021-09-14 13:05:29 +01:00
Hugo Sales
5eae3dc351
[CORE][DATABASE] Replace zero dates with CURRENT_TIMESTAMP and add defaults to all 'created' or 'modified' 
This commit is a port from v2's 9a515b9234 ([SCHEMA] Improve timestamp storage) to v3.

As explained by Alexei Sorokin:

Avoid the use of deprecated MariaDATABASE "zero dates" globally. If they're present
as attribute defaults somewhere, they will be replaced with NULL implicitly.
The existing "zero dates" in MariaDATABASE storage will be left intact and this
should not present any issues.

The "timestamp" type in table definitions now corresponds to DATETIME in
MariaDATABASE with "DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP", which
should be close enough to the original behaviour for compatibility purposes.
It is now the recommended type for "modified" attributes, because of the
update trigger on MariaDATABASE. But there is no such trigger implemented on
PostgreSQL as of this moment.
 2021-09-14 13:05:29 +01:00
Hugo Sales
25aeac80a3
[CORE][DATABASE] Restructure the database 2021-09-14 13:05:29 +01:00