PD.Relational Data Management - Revision history

Daniel Jumelet at 18:35, 27 November 2019

2019-11-27T18:35:23Z

← Older revision		Revision as of 18:35, 27 November 2019
Line 45:		Line 45:
	{{Pattern Definition Composition Row		{{Pattern Definition Composition Row
	\|function=FD.Archive		\|function=FD.Archive
	\|dataobjecttype=DOT.		\|dataobjecttype=DOT.Log
	\|choice=May		\|choice=May
	\|reason=Preservation of transaction logs, in order to be able to get further back in time regarding transactions.		\|reason=Preservation of transaction logs, in order to be able to get further back in time regarding transactions.

Daniel Jumelet at 18:34, 27 November 2019

2019-11-27T18:34:29Z

@@ Line 36: / Line 36: @@
 |choice=Must
 |reason=The Table Store offers the predefined storage structure. This is one of the key characteristics of relational data management.
 }}
 {{Pattern Definition Composition Row
@@ Line 70: / Line 82: @@
 |function=FD.Import
 |dataobjecttype=DOT.File
 |choice=Must
-|reason=Loading of data from a file, to store this data in a database. This is used to restore a database from a replica or to import a large dataset from another database (ETL). Because it does not require a connection between Data Engines, it offers more flexibility and security, compared to direct Data Engine interaction. In both cases, the proper interfaces should be available.
+|reason=Keeping track of events, activities, interactions that occur during database system operation.
 }}
 {{Table Ending}}

Daniel Jumelet at 17:36, 27 November 2019

2019-11-27T17:36:37Z

← Older revision		Revision as of 17:36, 27 November 2019
Line 69:		Line 69:
	{{Pattern Definition Composition Row		{{Pattern Definition Composition Row
	\|function=FD.Import		\|function=FD.Import
	\|dataobjecttype=DOT.		\|dataobjecttype=DOT.File
	\|choice=Must		\|choice=Must
	\|reason=Loading of data from a file, to store this data in a database. This is used to restore a database from a replica or to import a large dataset from another database (ETL). Because it does not require a connection between Data Engines, it offers more flexibility and security, compared to direct Data Engine interaction. In both cases, the proper interfaces should be available.		\|reason=Loading of data from a file, to store this data in a database. This is used to restore a database from a replica or to import a large dataset from another database (ETL). Because it does not require a connection between Data Engines, it offers more flexibility and security, compared to direct Data Engine interaction. In both cases, the proper interfaces should be available.
	}}		}}
	{{Table Ending}}		{{Table Ending}}

Daniel Jumelet at 17:35, 27 November 2019

2019-11-27T17:35:23Z

@@ Line 47: / Line 47: @@
 |dataobjecttype=DOT.Transaction
 |choice=May
-|reason=This function retains frequent issued transactions/queries, in order to improve performance.
+|reason=Retaining and keeping available of frequent issued transactions/queries, in order to improve performance.
 }}
 {{Table Ending}}

Daniel Jumelet at 16:28, 27 November 2019

2019-11-27T16:28:46Z

← Older revision		Revision as of 16:28, 27 November 2019
Line 14:		Line 14:
	* a "transaction mechanism", to enable interaction with other (instances of) data management facilities and applications.		* a "transaction mechanism", to enable interaction with other (instances of) data management facilities and applications.
	These elements are provided by the [[DOT.Data\|Data]] [[FD.Engine\|Engine]]. Data objects are stored using a predefined (structured) [[DOT.Data\|Data]] [[FD.Store\|Store]]. Both functions form the core of this Pattern.		These elements are provided by the [[DOT.Data\|Data]] [[FD.Engine\|Engine]]. Data objects are stored using a predefined (structured) [[DOT.Data\|Data]] [[FD.Store\|Store]]. Both functions form the core of this Pattern.








	~~{{Table Ending}}~~
	{{Pattern Realizes		{{Pattern Realizes
	\|service=SD.Application Database		\|service=SD.Application Database

Daniel Jumelet at 16:27, 27 November 2019

2019-11-27T16:27:41Z

← Older revision		Revision as of 16:27, 27 November 2019
Line 14:		Line 14:
	* a "transaction mechanism", to enable interaction with other (instances of) data management facilities and applications.		* a "transaction mechanism", to enable interaction with other (instances of) data management facilities and applications.
	These elements are provided by the [[DOT.Data\|Data]] [[FD.Engine\|Engine]]. Data objects are stored using a predefined (structured) [[DOT.Data\|Data]] [[FD.Store\|Store]]. Both functions form the core of this Pattern.		These elements are provided by the [[DOT.Data\|Data]] [[FD.Engine\|Engine]]. Data objects are stored using a predefined (structured) [[DOT.Data\|Data]] [[FD.Store\|Store]]. Both functions form the core of this Pattern.








			{{Table Ending}}
	{{Pattern Realizes		{{Pattern Realizes
	\|service=SD.Application Database		\|service=SD.Application Database
Line 49:		Line 58:
	\|reason=This function retains frequent issued transactions/queries, in order to improve performance.		\|reason=This function retains frequent issued transactions/queries, in order to improve performance.
	}}		}}
	~~{{Table Ending}}~~
	{{Table Ending}}		{{Table Ending}}

Daniel Jumelet at 16:21, 27 November 2019

2019-11-27T16:21:34Z

← Older revision		Revision as of 16:21, 27 November 2019
Line 1:		Line 1:
	{{Maturity		{{Maturity\|0
	\|maturity=0		\|maturity=0
	}}		}}

Daniel Jumelet at 16:19, 27 November 2019

2019-11-27T16:19:29Z

← Older revision		Revision as of 16:19, 27 November 2019
Line 1:		Line 1:
			{{Maturity
			\|maturity=0
			}}
	{{Pageheaderbox4PD		{{Pageheaderbox4PD
	\|name=Relational Data Management		\|name=Relational Data Management

Daniel Jumelet at 16:03, 27 November 2019

2019-11-27T16:03:27Z

← Older revision		Revision as of 16:03, 27 November 2019
Line 1:		Line 1:
	~~{{Maturity\|0}}~~
	{{Pageheaderbox4PD		{{Pageheaderbox4PD
	\|name=Relational Data Management		\|name=Relational Data Management
Line 47:		Line 46:
	\|reason=This function retains frequent issued transactions/queries, in order to improve performance.		\|reason=This function retains frequent issued transactions/queries, in order to improve performance.
	}}		}}
			{{Table Ending}}
	{{Table Ending}}		{{Table Ending}}

Daniel Jumelet at 15:30, 27 November 2019

2019-11-27T15:30:51Z

← Older revision		Revision as of 15:30, 27 November 2019
Line 25:		Line 25:
	{{Pattern Definition Composition Row		{{Pattern Definition Composition Row
	\|function=FD.Engine		\|function=FD.Engine
	\|~~datobjecttype~~=DOT.Data		\|dataobjecttype=DOT.Data
	\|choice=Must		\|choice=Must
	\|reason=The Data Engine is the heart of the pattern, as it offers the intelligence to control strictly structured data handling.		\|reason=The Data Engine is the heart of the pattern, as it offers the intelligence to control strictly structured data handling.
Line 31:		Line 31:
	{{Pattern Definition Composition Row		{{Pattern Definition Composition Row
	\|function=FD.Store		\|function=FD.Store
	\|~~datobjecttype~~=DOT.Table		\|dataobjecttype=DOT.Table
	\|choice=Must		\|choice=Must
	\|reason=The Table Store offers the predefined storage structure. This is one of the key characteristics of relational data management.		\|reason=The Table Store offers the predefined storage structure. This is one of the key characteristics of relational data management.
Line 37:		Line 37:
	{{Pattern Definition Composition Row		{{Pattern Definition Composition Row
	\|function=FD.Encryption		\|function=FD.Encryption
	\|~~datobjecttype~~=DOT.Traffic		\|dataobjecttype=DOT.Traffic
	\|choice=May		\|choice=May
	\|reason=When data is exchanged over unsecured data transport facilities, it might be a good measure to encrypt the data at engine level.		\|reason=When data is exchanged over unsecured data transport facilities, it might be a good measure to encrypt the data at engine level.
Line 43:		Line 43:
	{{Pattern Definition Composition Row		{{Pattern Definition Composition Row
	\|function=FD.Caching		\|function=FD.Caching
	\|~~datobjecttype~~=DOT.Transaction		\|dataobjecttype=DOT.Transaction
	\|choice=May		\|choice=May
	\|reason=This function retains frequent issued transactions/queries, in order to improve performance.		\|reason=This function retains frequent issued transactions/queries, in order to improve performance.
	}}		}}
	{{Table Ending}}		{{Table Ending}}