TGTable - Revision history

Tintinux: /* To create a new table */

2019-12-02T08:51:34Z

To create a new table

Tintinux: /* To create a new table */

2014-10-02T09:48:43Z

To create a new table

Tintinux: /* Deleting fields, index or constraints */

2014-08-28T17:19:14Z

Deleting fields, index or constraints

Tintinux: /* Deleting fields, index or constraints */

2014-06-13T07:59:50Z

Deleting fields, index or constraints

Tintinux: /* Deleting fields, index or constraints */

2014-06-13T07:59:01Z

Deleting fields, index or constraints

Tintinux: /* To create a new table */

2014-03-24T17:17:42Z

To create a new table

Tintinux: /* Deleting fields, index or constraints */

2013-02-07T18:49:57Z

Deleting fields, index or constraints

Tintinux: /* To create a new table */

2012-12-06T19:14:11Z

To create a new table

Tintinux: /* To read or insert data */

2012-11-21T09:24:50Z

To read or insert data

Tintinux: /* Deleting fields, index or constraints */

2012-10-20T17:06:07Z

Deleting fields, index or constraints

@@ Line 30: / Line 30: @@
 ** Add '''all''' other fields as usual.
 ** Copy and paste the index and constraint instructions in the property ''Properties'', and remove quotes and commas at the end of each line
-** In DataModule1.DbAfterConnect event, add Lazarus instruction : TGTable.Check for the new table, when a reorganization is requested.
+** In unitcheckdatabase.pas, add Lazarus instruction : TGTable.Check for the new table, to trigger automatic creation or reorganization.
-* To test, select another database not containing the new table, or delete the new table in the database where it was created.
+* To test, select another database not containing the new table, or delete the new table in the database where it was just created.
 ** Run the reorganization : the table should be re-created with the specified properties
 ** Check the structure of the table in the query browser

@@ Line 10: / Line 10: @@
 This is for a new functionnality in the application (only in the trunk version).
-In order to have sources easy to read, avoid spaces in table names and fields. This way, quotes are not required.
+In order to have sources easy to read, and for easier compatibility with different DBMS, avoid spaces in table names and fields. This way, quotes are not required.
 * Create the table and all it's fields, index and constraints with MySql Query Browser, MySql Workbench, or any other MySql client (not PostgreSQL).
@@ Line 20: / Line 20: @@
 *** Date, Datetime
 *** LongText
-**Always start with an '''Id''' field, Autoinc and Primary key. In Gestinux datamodel all relations are made between such Id fields.
+**Always start with an '''Id''' field, Autoinc and Primary key. In Gestinux datamodel all relations are made between such Id fields ([[upgrade_to_id|there are exceptions]]).
 **Always end with 2 fields :
 *** '''UpdateDate''' ''DATETIME NULL''

@@ Line 48: / Line 48: @@
 The rule is
 * version N must accept a database created in version N-1 with automatic reorganization.
-* version N-1 must work on a database created by version N.
+* version N-1 must work on a database created by version N with automatic reorganization.
 * version N+2 will not work on a database created by version N, and version N will not work on a database created by version N+2.
-When the difference is greater than 1, installing intermediate version is required.
+When the difference is greater than 1, installing intermediate version is required. They are available for [[https://sourceforge.net/projects/gestinux/files/Old%20versions/  download]].
-Starting with Gestinux 1.1, this is checked when a database is connected for the first time.
+This is checked when a database is connected for the first time.
-If an index is no more useful, you can call TGTable.DeleteIndex during database reorganization. No error while be raised if the index doesn't exists. Again, this must be done only if this don't prevent previous version to work.
+If an index is no more useful, the AfterConnect event of the datamodule can call TGTable.DeleteIndex. No error while be raised if the index doesn't exists.
 If a constraint is no more useful, you can execute after the reorganization a SQL Script to delete it. A method similar to DeleteIndex should be written.

@@ Line 49: / Line 49: @@
 * version N must accept a database created in version N-1 with automatic reorganization.
 * version N-1 must work on a database created by version N.
-* version N+2 will not work on a database created by version N.x, and version N.x will not work on a database created by version N+2.
+* version N+2 will not work on a database created by version N, and version N will not work on a database created by version N+2.
 When the difference is greater than 1, installing intermediate version is required.

@@ Line 47: / Line 47: @@
 The rule is
-* version N.x must accept a database created in version N-1.x with automatic reorganization.
+* version N must accept a database created in version N-1 with automatic reorganization.
-* version N-1.x must work on a database created by version N.x.
+* version N-1 must work on a database created by version N.
-* version N+2.x will not work on a database created by version N.x, and version N.x will not work on a database created by version N+2.x. When the difference is greater than 1, installing intermediate version is required.
+* version N+2 will not work on a database created by version N.x, and version N.x will not work on a database created by version N+2.
-If an index is no more useful, you can call TGTable.DeleteIndex during database reorganization. No error while be raised if the index doesn't exists.
+When the difference is greater than 1, installing intermediate version is required.
 If a constraint is no more useful, you can execute after the reorganization a SQL Script to delete it. A method similar to DeleteIndex should be written.

@@ Line 21: / Line 21: @@
 *** LongText
 **Always start with an '''Id''' field, Autoinc and Primary key. In Gestinux datamodel all relations are made between such Id fields.
-**Always end with an '''UpdateDate''' field, ''TimeStamp default current_timestamp on update current_timestamp''
+**Always end with 2 fields :
 * Drop a TGTable object in Datamodule, with connexion set to open the previous database.
 ** Create a new computed field AutoInc

@@ Line 51: / Line 51: @@
 If an index is no more useful, you can call TGTable.DeleteIndex during database reorganization. No error while be raised if the index doesn't exists.
-If ar constraint is no more useful, you can execute after the reorganization a SQL Script to delete it. A method similar to DeleteIndex should be written.
+If a constraint is no more useful, you can execute after the reorganization a SQL Script to delete it. A method similar to DeleteIndex should be written.
 If a field is no more useful, it should be kept and updated until the n+2 stable version is out, to allow backward compatibility.

@@ Line 12: / Line 12: @@
 In order to have sources easy to read, avoid spaces in table names and fields. This way, quotes are not required.
-After a table is created, the minimal database version number must be incremented in the datamodule. This ensure a reorganization the first time the database is opened with the new program.
+* Create the table and all it's fields, index and constraints with MySql Query Browser, MySql Workbench, or any other MySql client (not PostgreSQL).
 **The following types can be used only. If other types are necessary, some development must be done.
 *** Integer Autoinc
@@ Line 21: / Line 19: @@
 *** Timestamp
 *** Date, Datetime
-*** Blob
+*** LongText
 **Always start with an '''Id''' field, Autoinc and Primary key. In Gestinux datamodel all relations are made between such Id fields.
 **Always end with an '''UpdateDate''' field, ''TimeStamp default current_timestamp on update current_timestamp''
@@ Line 27: / Line 25: @@
 ** Create a new computed field AutoInc
 ** Because of a bug, correct it's wrong name to <TableName>Id
-** set it Required and set the FieldKind to fkData.
+** Set it Required and set the FieldKind to fkData.
 ** Add '''all''' other fields as usual.
-** Write the index and constraint instructions in the property ''Properties''.
+** Copy and paste the index and constraint instructions in the property ''Properties'', and remove quotes and commas at the end of each line
-** Copy and paste the MySql Syntaxe, remove quotes and commas at the end of the line
+** In DataModule1.DbAfterConnect event, add Lazarus instruction : TGTable.Check for the new table, when a reorganization is requested.
 * To test, select another database not containing the new table, or delete the new table in the database where it was created.
 ** Run the reorganization : the table should be re-created with the specified properties
 ** Check the structure of the table in the query browser
 == To add fields, index, constraints in an existing table ==

@@ Line 61: / Line 61: @@
 Do not use TGTable.
 To read data, use only [[TGQuery]].
-To insert, update or delete, use methods of [[TGConnection]]
+To insert, update or delete, use methods of [[TGDbConnection]]

@@ Line 45: / Line 45: @@
 This is not and will not be automated.
-If an index or constraint is no more useful, you can execute after the reorganization a SQL Script to delete it
 If a field is no more useful, it should be kept and updated until the n+2 stable version is out, to allow backward compatibility.
 Never re-use an previously used name.