11 Commits

Author	SHA1	Message	Date
Hugo Sales	2c9bd3575b	[AUTOGENERATED] Update auto generated code in entities	2021-04-14 15:37:23 +00:00
Hugo Sales	256169a3c4	[GIT] Change my email to the new one in all files and bump copyright year	2021-04-14 15:37:23 +00:00
Hugo Sales	b1cb923036	Ensure group table name is quoted, as it's a reserved word in postgreSQL	2021-04-14 15:37:23 +00:00
Hugo Sales	5ed2abaf64	[ENTITY] Add Entity base class to all entities	2021-04-14 15:37:22 +00:00
Hugo Sales	5b11c26e79	[AUTOGENERATED] Update autogenerated code	2021-04-14 15:37:22 +00:00
Hugo Sales	e0af29fd5e	[CORE] Data Representation and Modelling refactor	2021-04-14 15:37:22 +00:00
Hugo Sales	a498134b13	[AUTOGENERATED] Update autogenerated code	2021-04-14 15:37:22 +00:00
Hugo Sales	9a9ac8b55f	[AUTOGENERATED] Update autogenerated code	2021-04-14 15:37:21 +00:00
Hugo Sales	a574971f0b	[AUTOGENERATED] Update autogenerated code	2021-04-14 15:37:21 +00:00
Hugo Sales	3a6b4cca1e	[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-04-14 15:37:21 +00:00
Hugo Sales	6fe35833e7	[CORE][DATABASE] Restructure the database	2021-04-14 15:37:21 +00:00