Sprachen und Programmierregeln - Revision history

Eldy: /* Communication between business logic - data (ORM) */

2024-03-08T10:24:44Z

Communication between business logic - data (ORM)

← Older revision		Revision as of 10:24, 8 March 2024
Line 536:		Line 536:
	*The '''Table And Row Data Gateway'''		*The '''Table And Row Data Gateway'''

	This is the most simple. You have one class per table and each class is a link to the table with CRUD methods (~~Ceate~~, Read, Update, Delete). A class instance is a record in the table. The class contains only code to reach lines and fields of table.		This is the most simple. You have one class per table and each class is a link to the table with CRUD methods (Create, Read, Update, Delete). A class instance is a record in the table. The class contains only code to reach lines and fields of table.

	Example: This mode is used by some ORM Frameworks, like '''iBatis''' (http://ibatis.apache.org/).		Example: This mode is used by some ORM Frameworks, like '''iBatis''' (http://ibatis.apache.org/).
Line 551:		Line 551:
	More "purist" on paper (closer of business), this method also has the disadvantage of being more complex in practice.		More "purist" on paper (closer of business), this method also has the disadvantage of being more complex in practice.

	Example: This is the choice if you use the ORM Framework '''Propel''' (~~http~~://~~propel.phpdb~~.org~~/trac~~/). We find this model in heavier applications, based on this ORM among others.		Example: This is the choice if you use the ORM Framework '''Propel''' (https://propelorm.org/). We find this model in heavier applications, based on this ORM among others.

	-> For Dolibarr development, it is recommended to use the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating technical architecture. It is by this way that the development, understanding of code and technical maintenance and / or business ~~behaviour~~ seems the more productive (this is however an ongoing debate between the purists and the pragmatists, debate in which nobody can really be right, because it depends on the objectives).		-> For Dolibarr development, it is recommended to use the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating technical architecture. It is by this way that the development, understanding of code and technical maintenance and / or business behavior seems the more productive (this is however an ongoing debate between the purists and the pragmatists, debate in which nobody can really be right, because it depends on the objectives).

Udo.tamm: /* Versionen */

2024-03-04T18:37:11Z

Versionen

Show changes

Eldy at 14:18, 10 November 2023

2023-11-10T14:18:50Z

← Older revision		Revision as of 14:18, 10 November 2023
Line 43:		Line 43:
	*Dolibarr ist in PHP geschrieben und unterstützt alle Versionen von PHP, welche höher sind, als {{PHPMinVersion}}. Alle Dateien müssen mit der Erweiterung .php enden.		*Dolibarr ist in PHP geschrieben und unterstützt alle Versionen von PHP, welche höher sind, als {{PHPMinVersion}}. Alle Dateien müssen mit der Erweiterung .php enden.

	*Die Verwendung von PHP superglobalen Variablen muss über die festgelegten Operatoren $~~_COOKIES~~, $_SERVER, $_ENV erfolgen.		*Die Verwendung von PHP superglobalen Variablen muss über die festgelegten Operatoren $_COOKIE, $_SERVER, $_ENV erfolgen.
	*Allerdings muss die Dolibarr-Funktion GETPOST () verwendet werden, um den Inhalt von $_GET oder $_POST abzurufen.		*Allerdings muss die Dolibarr-Funktion GETPOST () verwendet werden, um den Inhalt von $_GET oder $_POST abzurufen.

Gschratzer: /* Tabellen- und Feldstruktur */

2021-10-22T07:18:08Z

Tabellen- und Feldstruktur

← Older revision		Revision as of 07:18, 22 October 2021
Line 124:		Line 124:
	=SQL Standards=		=SQL Standards=

	==~~Tabellen- und Feldstruktur~~==		==Dateiformat DDL==
	Dateien, die die Definition der Datenbankstruktur enthalten (DDL-Dateien), benötigen 2 pro Tabelle:		Dateien, die die Definition der Datenbankstruktur enthalten (DDL-Dateien), benötigen 2 pro Tabelle:
	*Die erste Datei definiert die Tabelle und ihre Felder. Der Dateiname enthält den Tabellennamen, z. B. so: llx_mytable.sql		*Die erste Datei definiert die Tabelle und ihre Felder. Der Dateiname enthält den Tabellennamen, z. B. so: llx_mytable.sql

Gschratzer: /* Table and fields structures */

2021-10-22T07:16:47Z

Table and fields structures

← Older revision		Revision as of 07:16, 22 October 2021
Line 196:		Line 196:
	</syntaxHighlight>		</syntaxHighlight>

	==~~Table and fields structures~~==		==Tabellen- und Feldstrukturen==

	*Structure of tables.		*Structure of tables.

Gschratzer: /* SQL Regeln */

2021-10-22T07:15:45Z

SQL Regeln

← Older revision		Revision as of 07:15, 22 October 2021
Line 122:		Line 122:
	{{TemplatePHPFields}}		{{TemplatePHPFields}}

	=SQL ~~Regeln~~=		=SQL Standards=

	==~~DDL file format~~==		==Tabellen- und Feldstruktur==
	~~Files containing definition of the database structure~~ (DDL ~~files~~) ~~must be '''~~2 ~~per table'''~~:		Dateien, die die Definition der Datenbankstruktur enthalten (DDL-Dateien), benötigen 2 pro Tabelle:
			*Die erste Datei definiert die Tabelle und ihre Felder. Der Dateiname enthält den Tabellennamen, z. B. so: llx_mytable.sql
			Alle Tabellen sind mit einem Präfix versehen, um Namenskonflikte zu vermeiden. Das Präfix kann bei der Installation geändert werden. Der Standardwert ist llx_.

	*The first file defines the table and its fields. ~~The file name contains the table name~~, ~~e.g~~. ~~like this: <tt>llx_''mytable''~~.sql~~</tt>~~		Zu jedem Feld wird ein Kommentar hinzugefügt, um seine Verwendung zu erläutern.
			Die zweite Datei definiert alle Fremdschlüssel, Leistungsindizes oder andere Einschränkungen und der Dateiname lautet: llx_mytable.key.sql

	~~A comment will be added for each field to explain its usage.~~		Diese Dateien müssen im Verzeichnis install/mysql/tables für alle Standarddateien oder im Verzeichnis mymodule/tables für Tabellen, die von einem externen Modul bereitgestellt werden, gespeichert werden.

	*The second file defines all foreign keys, performance indexes or other constraints and the file name will be like: <tt>llx_''mytable''.key.sql</tt>

	~~These files must be stored in the directory '''~~install/mysql/tables~~''' for all standard files or '''~~mymodule/tables~~''' for tables provided by an external module~~.

	Example: '''file for creating the table llx_mytable will be llx_mytable.sql''':		Example: '''file for creating the table llx_mytable will be llx_mytable.sql''':
Line 170:		Line 169:
	fk_user_mod integer NOT NULL, -- Last updater, foreign key of llx_user		fk_user_mod integer NOT NULL, -- Last updater, foreign key of llx_user
	import_key varchar(14) -- Use by import process		import_key varchar(14) -- Use by import process
	)type=innodb;		)type=innodb;</syntaxHighlight>
	</syntaxHighlight>

	Example: '''file for creating keys/indexes for the table llx_mytable will be llx_mytable.key.sql''':		Example: '''file for creating keys/indexes for the table llx_mytable will be llx_mytable.key.sql''':

Eldy at 11:35, 11 June 2021

2021-06-11T11:35:15Z

← Older revision		Revision as of 11:35, 11 June 2021
Line 554:		Line 554:

	-> For Dolibarr development, it is recommended to use the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating technical architecture. It is by this way that the development, understanding of code and technical maintenance and / or business behaviour seems the more productive (this is however an ongoing debate between the purists and the pragmatists, debate in which nobody can really be right, because it depends on the objectives).		-> For Dolibarr development, it is recommended to use the connection mode '''Active Record''', which offers the advantages of a model close to the business without having the complexity, without obfuscating technical architecture. It is by this way that the development, understanding of code and technical maintenance and / or business behaviour seems the more productive (this is however an ongoing debate between the purists and the pragmatists, debate in which nobody can really be right, because it depends on the objectives).
	~~[[Category:Development]]~~

Eldy at 11:33, 11 June 2021

2021-06-11T11:33:30Z

← Older revision		Revision as of 11:33, 11 June 2021
Line 287:		Line 287:

	Example:		Example:
	<~~source~~ lang="sql">		<syntaxHighlight lang="sql">
	Good: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)		Good: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', 412.62)
	Bad: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')		Bad: INSERT INTO table_1 (field_txt, field_num) VALUES ('txt', '412.62')
	</~~source~~>		</syntaxHighlight>

	Note, problem of float numbers is same problem on all langauges and not only when inserting data into database. It occurs also with any language when you work on "real" numbers, so numbers must be, as soon as they are affected, cleaned with function price2num with second parameter defined to :		Note, problem of float numbers is same problem on all langauges and not only when inserting data into database. It occurs also with any language when you work on "real" numbers, so numbers must be, as soon as they are affected, cleaned with function price2num with second parameter defined to :

Eldy at 11:33, 11 June 2021

2021-06-11T11:33:11Z

← Older revision		Revision as of 11:33, 11 June 2021
Line 137:		Line 137:
	Example: '''file for creating the table llx_mytable will be llx_mytable.sql''':		Example: '''file for creating the table llx_mytable will be llx_mytable.sql''':

	<~~source~~ lang="sql">		<syntaxHighlight lang="sql">
	-- ===========================================================================		-- ===========================================================================
	-- Copyright (C) 2013 Author <email@author.com>		-- Copyright (C) 2013 Author <email@author.com>
Line 171:		Line 171:
	import_key varchar(14) -- Use by import process		import_key varchar(14) -- Use by import process
	)type=innodb;		)type=innodb;
	</~~source~~>		</syntaxHighlight>

	Example: '''file for creating keys/indexes for the table llx_mytable will be llx_mytable.key.sql''':		Example: '''file for creating keys/indexes for the table llx_mytable will be llx_mytable.key.sql''':

Eldy at 11:32, 11 June 2021

2021-06-11T11:32:49Z

Show changes