Database refactoring - Revision history

YesI'mOnFire: Restored revision 1232064665 by 192.223.241.26 (talk)

2024-08-10T14:58:18Z

Restored revision 1232064665 by 192.223.241.26 (talk)

← Previous revision		Revision as of 14:58, 10 August 2024
Line 1:		Line 1:
	A '''database refactoring''' is a simple change to a [[database schema]] that improves its design while retaining both its behavioral and informational semantics. Database refactoring does not change the way data is interpreted or used and does not fix [[software bug\|bug]]s or add new functionality. Every refactoring to a database leaves the system in a working state, thus not causing maintenance lags, provided the meaningful data exists in the production environment.		A '''database refactoring''' is a simple change to a [[database schema]] that improves its design while retaining both its behavioral and informational semantics. Database refactoring does not change the way data is interpreted or used and does not fix [[software bug\|bug]]s or add new functionality. Every refactoring to a database leaves the system in a working state, thus not causing maintenance lags, provided the meaningful data exists in the production environment.

	A database refactoring is conceptually more difficult than a code refactoring; code refactorings only need to maintain behavioral semantics, while database refactorings also must maintain informational semantics.		A database refactoring is conceptually more difficult than a [[code refactoring]]; code refactorings only need to maintain behavioral semantics while database refactorings also must maintain informational semantics.

	~~'''<u>~~A database schema is typically refactored for one of several reasons:~~</u>'''~~		A database schema is typically refactored for one of several reasons:
		⚫	# To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.

		⚫	# To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for [[database normalization]] of an existing production database, typically to "clean up" the design of the database.
⚫	* To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.
		⚫	# To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.
⚫	* To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for database normalization of an existing production database, typically to "clean up" the design of the database.
⚫	* To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.

	==Categories of database refactoring==		==Categories of database refactoring==
	{{Tone\|date=July 2024}}		{{Tone\|date=July 2024}}
			In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN\|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>
	In 2006, Scott Ambler and Pramod Sadalage described the following categories of database refactoring:
	* Architecture Refactoring		* Architecture Refactoring
	::A change ~~that~~ improves the overall manner in which external programs interact with a database.		::A change which improves the overall manner in which external programs interact with a database.
	Methods of ~~the~~ Architecture Refactoring category: Add CRUD Methods; Add Mirror Table; Add Read Method; Encapsulate Table ~~with~~ View; Introduce Calculation Method; Introduce Index; Introduce Read-Only Table; Migrate Method ~~from~~ Database; Migrate Method to Database; Replace Method(s) ~~with~~ View; Replace View ~~with~~ ~~Method~~(s); Use Official Data Source.		Methods of Architecture Refactoring category: Add CRUD Methods; Add Mirror Table; Add Read Method; Encapsulate Table With View; Introduce Calculation Method; Introduce Index; Introduce Read Only Table; Migrate Method From Database; Migrate Method To Database; Replace Method(s) With View; Replace View With Methods(s); Use Official Data Source.
	* Structural Refactoring		* Structural Refactoring
	::~~'''<u>~~A change to the table structure of your database schema.~~</u>'''~~		::A change to the table structure of your database schema.
	Methods of ~~the~~ Structural Refactoring category: Drop Column; Drop Table; Drop View; Introduce Calculated Column; Introduce Surrogate Key; Merge Columns; Merge Tables; Move Column; Rename Column; Rename Table; Rename View; Replace LOB ~~with~~ Table; Replace Column; Replace One-to-Many ~~with~~ Associative Tables; Replace Surrogate Key ~~with~~ Natural Key; Split Column; Split Table.		Methods of Structural Refactoring category: Drop Column; Drop Table; Drop View; Introduce Calculated Column; Introduce Surrogate Key; Merge Columns; Merge Tables; Move Column; Rename Column; Rename Table; Rename View; Replace LOB With Table; Replace Column; Replace One-To-Many With Associative Tables; Replace Surrogate Key With Natural Key; Split Column; Split Table.
	* Data Quality Refactoring		* Data Quality Refactoring
	::A change ~~that~~ improves and ensures the consistency and usage of the values stored in the database.		::A change which improves and/or ensures the consistency and usage of the values stored within the database.
	Methods of ~~the~~ Data Quality Refactoring category: Add Lookup Table; Apply Standard Codes; Apply Standard Type; Consolidate Key Strategy; Drop Column Constraint; Drop Default Value; Drop Non-Nullable; Introduce Column Constraint; Introduce Common Format; Introduce Default Value; Make Column Non-Nullable; Move Data; Replace Type Code ~~with~~ Property Flags.		Methods of Data Quality Refactoring category: Add Lookup Table; Apply Standard Codes; Apply Standard Type; Consolidate Key Strategy; Drop Column Constraint; Drop Default Value; Drop Non Nullable; Introduce Column Constraint; Introduce Common Format; Introduce Default Value; Make Column Non Nullable; Move Data; Replace Type Code With Property Flags.

	* Referential Integrity Refactoring		* Referential Integrity Refactoring
		⚫	::A change which ensures that a referenced row exists within another table and/or that ensures that a row which is no longer needed is removed appropriately.
	::
	Methods of Referential Integrity Refactoring category: Add Foreign Key Constraint; Add Trigger for Calculated Column; Drop Foreign Key Constraint; Introduce Cascading Delete; Introduce Hard Delete; Introduce Soft Delete; Introduce Trigger for History.		Methods of Referential Integrity Refactoring category: Add Foreign Key Constraint; Add Trigger for Calculated Column; Drop Foreign Key Constraint; Introduce Cascading Delete; Introduce Hard Delete; Introduce Soft Delete; Introduce Trigger for History.
	* Transformation		* Transformation
			::A change which changes the semantics of your database schema by adding new elements to it or by modifying existing elements.
⚫	::A change ~~that~~ ensures a referenced row exists within another table and/or ensures that a row no longer needed is removed appropriately.
	Methods of ~~the~~ Transformation category: Insert Data; Introduce New Column; Introduce New Table; Introduce View; Update Data		Methods of Transformation category: Insert Data; Introduce New Column; Introduce New Table; Introduce View; Update Data.
	* Method Refactoring		* Method Refactoring
	::A change ~~that~~ improves the quality of a stored procedure, stored function, or trigger.		::A change which improves the quality of a stored procedure, stored function, or trigger.
	Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.		Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.

			In 2019 Vladislav Struzik supplemented the categories of database refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>
	In 2019, Vladislav Struzik supplemented the categories of database refactoring with a new one:
	* Access Refactoring		* Access Refactoring
	::A change ~~that~~ relates to data access.		::A change which relates to data access.
	Methods of the Access Refactoring category: Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.		Methods of the Access Refactoring category:<ref name="access_refactoring_2">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік, С. В. Грибков, В. В. Чобану // Наукові праці НУХТ. – Т. 26, № 2. – 2020. – С. 31–49. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31515</ref><ref name="access_refactoring_medium"> ''Vladislav Struzik, PhD'' Refactoring: yesterday, today, tomorrow. URL: https://medium.com/@struzik/refactoring-yesterday-today-tomorrow-7fc8c845cfb1 </ref> Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.

	==Process of database refactoring==		==Process of database refactoring==
Line 41:		Line 39:
	# How a single refactoring is implemented		# How a single refactoring is implemented
	# How database refactorings are tracked and shared within organizations		# How database refactorings are tracked and shared within organizations
	# How a series of database refactorings is applied		# How a series of database refactorings are applied

	==See also==		==See also==

Harsha 2005 MT: changed some word and added commas to easy reading and changed to be easy reading text

2024-08-10T14:56:13Z

changed some word and added commas to easy reading and changed to be easy reading text

← Previous revision		Revision as of 14:56, 10 August 2024
Line 1:		Line 1:
	A '''database refactoring''' is a simple change to a [[database schema]] that improves its design while retaining both its behavioral and informational semantics. Database refactoring does not change the way data is interpreted or used and does not fix [[software bug\|bug]]s or add new functionality. Every refactoring to a database leaves the system in a working state, thus not causing maintenance lags, provided the meaningful data exists in the production environment.		A '''database refactoring''' is a simple change to a [[database schema]] that improves its design while retaining both its behavioral and informational semantics. Database refactoring does not change the way data is interpreted or used and does not fix [[software bug\|bug]]s or add new functionality. Every refactoring to a database leaves the system in a working state, thus not causing maintenance lags, provided the meaningful data exists in the production environment.

	A database refactoring is conceptually more difficult than a [[code refactoring]]; code refactorings only need to maintain behavioral semantics while database refactorings also must maintain informational semantics.		A database refactoring is conceptually more difficult than a code refactoring; code refactorings only need to maintain behavioral semantics, while database refactorings also must maintain informational semantics.

	A database schema is typically refactored for one of several reasons:		'''<u>A database schema is typically refactored for one of several reasons:</u>'''

	# To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.
	# To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for [[database normalization]] of an existing production database, typically to "clean up" the design of the database.		* To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.
			* To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for database normalization of an existing production database, typically to "clean up" the design of the database.
	# To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.		* To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.

	==Categories of database refactoring==		==Categories of database refactoring==
	{{Tone\|date=July 2024}}		{{Tone\|date=July 2024}}
			In 2006, Scott Ambler and Pramod Sadalage described the following categories of database refactoring:
	In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN\|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>
	* Architecture Refactoring		* Architecture Refactoring
	::A change ~~which~~ improves the overall manner in which external programs interact with a database.		::A change that improves the overall manner in which external programs interact with a database.
	Methods of Architecture Refactoring category: Add CRUD Methods; Add Mirror Table; Add Read Method; Encapsulate Table ~~With~~ View; Introduce Calculation Method; Introduce Index; Introduce Read Only Table; Migrate Method ~~From~~ Database; Migrate Method To Database; Replace Method(s) ~~With~~ View; Replace View ~~With~~ ~~Methods~~(s); Use Official Data Source.		Methods of the Architecture Refactoring category: Add CRUD Methods; Add Mirror Table; Add Read Method; Encapsulate Table with View; Introduce Calculation Method; Introduce Index; Introduce Read-Only Table; Migrate Method from Database; Migrate Method to Database; Replace Method(s) with View; Replace View with Method(s); Use Official Data Source.
	* Structural Refactoring		* Structural Refactoring
	::A change to the table structure of your database schema.		::'''<u>A change to the table structure of your database schema.</u>'''
	Methods of Structural Refactoring category: Drop Column; Drop Table; Drop View; Introduce Calculated Column; Introduce Surrogate Key; Merge Columns; Merge Tables; Move Column; Rename Column; Rename Table; Rename View; Replace LOB ~~With~~ Table; Replace Column; Replace One-To-Many ~~With~~ Associative Tables; Replace Surrogate Key ~~With~~ Natural Key; Split Column; Split Table.		Methods of the Structural Refactoring category: Drop Column; Drop Table; Drop View; Introduce Calculated Column; Introduce Surrogate Key; Merge Columns; Merge Tables; Move Column; Rename Column; Rename Table; Rename View; Replace LOB with Table; Replace Column; Replace One-to-Many with Associative Tables; Replace Surrogate Key with Natural Key; Split Column; Split Table.
	* Data Quality Refactoring		* Data Quality Refactoring
	::A change ~~which~~ improves and~~/or~~ ensures the consistency and usage of the values stored ~~within~~ the database.		::A change that improves and ensures the consistency and usage of the values stored in the database.
	Methods of Data Quality Refactoring category: Add Lookup Table; Apply Standard Codes; Apply Standard Type; Consolidate Key Strategy; Drop Column Constraint; Drop Default Value; Drop Non Nullable; Introduce Column Constraint; Introduce Common Format; Introduce Default Value; Make Column Non Nullable; Move Data; Replace Type Code ~~With~~ Property Flags.		Methods of the Data Quality Refactoring category: Add Lookup Table; Apply Standard Codes; Apply Standard Type; Consolidate Key Strategy; Drop Column Constraint; Drop Default Value; Drop Non-Nullable; Introduce Column Constraint; Introduce Common Format; Introduce Default Value; Make Column Non-Nullable; Move Data; Replace Type Code with Property Flags.

	* Referential Integrity Refactoring		* Referential Integrity Refactoring
			::
⚫	::A change ~~which~~ ensures ~~that~~ a referenced row exists within another table and/or ~~that~~ ensures that a row ~~which is~~ no longer needed is removed appropriately.
	Methods of Referential Integrity Refactoring category: Add Foreign Key Constraint; Add Trigger for Calculated Column; Drop Foreign Key Constraint; Introduce Cascading Delete; Introduce Hard Delete; Introduce Soft Delete; Introduce Trigger for History.		Methods of Referential Integrity Refactoring category: Add Foreign Key Constraint; Add Trigger for Calculated Column; Drop Foreign Key Constraint; Introduce Cascading Delete; Introduce Hard Delete; Introduce Soft Delete; Introduce Trigger for History.
	* Transformation		* Transformation
		⚫	::A change that ensures a referenced row exists within another table and/or ensures that a row no longer needed is removed appropriately.
	::A change which changes the semantics of your database schema by adding new elements to it or by modifying existing elements.
	Methods of Transformation category: Insert Data; Introduce New Column; Introduce New Table; Introduce View; Update Data.		Methods of the Transformation category: Insert Data; Introduce New Column; Introduce New Table; Introduce View; Update Data
	* Method Refactoring		* Method Refactoring
	::A change ~~which~~ improves the quality of a stored procedure, stored function, or trigger.		::A change that improves the quality of a stored procedure, stored function, or trigger.
	Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.		Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.

			In 2019, Vladislav Struzik supplemented the categories of database refactoring with a new one:
	In 2019 Vladislav Struzik supplemented the categories of database refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>
	* Access Refactoring		* Access Refactoring
	::A change ~~which~~ relates to data access.		::A change that relates to data access.
	Methods of the Access Refactoring category:<ref name="access_refactoring_2">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік, С. В. Грибков, В. В. Чобану // Наукові праці НУХТ. – Т. 26, № 2. – 2020. – С. 31–49. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31515</ref><ref name="access_refactoring_medium"> ''Vladislav Struzik, PhD'' Refactoring: yesterday, today, tomorrow. URL: https://medium.com/@struzik/refactoring-yesterday-today-tomorrow-7fc8c845cfb1 </ref> Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.		Methods of the Access Refactoring category: Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.

	==Process of database refactoring==		==Process of database refactoring==
Line 39:		Line 41:
	# How a single refactoring is implemented		# How a single refactoring is implemented
	# How database refactorings are tracked and shared within organizations		# How database refactorings are tracked and shared within organizations
	# How a series of database refactorings ~~are~~ applied		# How a series of database refactorings is applied

	==See also==		==See also==

192.223.241.26: /* Categories of database refactoring */

2024-07-01T19:18:11Z

Categories of database refactoring

← Previous revision		Revision as of 19:18, 1 July 2024
Line 9:		Line 9:

	==Categories of database refactoring==		==Categories of database refactoring==
			{{Tone\|date=July 2024}}
	In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN\|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>		In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN\|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>
	* Architecture Refactoring		* Architecture Refactoring

Codename Noreste: Reverting edit(s) by 203.215.181.210 (talk) to rev. 1156555845 by Frap: test edits (RW 16.1)

2023-06-16T05:11:07Z

Reverting edit(s) by 203.215.181.210 (talk) to rev. 1156555845 by Frap: test edits (RW 16.1)

← Previous revision		Revision as of 05:11, 16 June 2023
Line 29:		Line 29:
	Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.		Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.

	In 2019 Vladislav Struzik supplemented the categories of ~~datavvvvvbase~~ refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>		In 2019 Vladislav Struzik supplemented the categories of database refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>
	* Access Refactoring		* Access Refactoring
	::A change which relates to data access.		::A change which relates to data access.

203.215.181.210: x

2023-06-16T05:10:50Z

← Previous revision		Revision as of 05:10, 16 June 2023
Line 29:		Line 29:
	Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.		Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.

	In 2019 Vladislav Struzik supplemented the categories of ~~database~~ refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>		In 2019 Vladislav Struzik supplemented the categories of datavvvvvbase refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>
	* Access Refactoring		* Access Refactoring
	::A change which relates to data access.		::A change which relates to data access.

Frap: /* Categories of Database Refactoring */ MOS:HEAD

2023-05-23T12:48:49Z

Categories of Database Refactoring: MOS:HEAD

← Previous revision		Revision as of 12:48, 23 May 2023
Line 8:		Line 8:
	# To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.		# To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.

	==Categories of ~~Database~~ ~~Refactoring~~==		==Categories of database refactoring==
	In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN\|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>		In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN\|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>
	* Architecture Refactoring		* Architecture Refactoring

GünniX: v2.05 - Fix errors for CW project (Reference before punctuation - Unbalanced quotes in ref name or illegal character.)

2023-02-08T05:31:23Z

v2.05 - Fix errors for CW project (Reference before punctuation - Unbalanced quotes in ref name or illegal character.)

← Previous revision		Revision as of 05:31, 8 February 2023
Line 9:		Line 9:

	==Categories of Database Refactoring==		==Categories of Database Refactoring==
	In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - ~~ISBN‎~~ 978-0321774514</ref> describe the following categories of database refactoring<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>:		In 2006 Scott Ambler, Pramod Sadalage<ref name="database_refactoring"> ''Scott Ambler, Pramod Sadalage'' Refactoring Databases: Evolutionary Database Design - Addison-Wesley Professional; 1st edition (March 3, 2006) - 384 p. - {{ISBN\|978-0321774514}}</ref> describe the following categories of database refactoring:<ref name="embler_db_refactoring">''Scott Ambler'' Catalog of Database Refactorings - Agile Data - URL: http://agiledata.org/essays/databaseRefactoringCatalog.html</ref>
	* Architecture Refactoring		* Architecture Refactoring
	::A change which improves the overall manner in which external programs interact with a database.		::A change which improves the overall manner in which external programs interact with a database.
Line 29:		Line 29:
	Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.		Methods of the Method Refactoring category: Parameterize Methods; Remove Parameter; Rename Method; Reorder Parameters; Replace Parameter with Explicit Methods; Consolidate Conditional Expression; Decompose Conditional; Extract Method; Introduce Variable; Remove Control Flag; Remove Middle Man; Replace Literal with Table Lookup; Replace Nested; Conditional with Guard Clauses; Split Temporary Variable; Substitute Algorithm.

	In 2019 Vladislav Struzik supplemented the categories of database refactoring with a new one<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>:		In 2019 Vladislav Struzik supplemented the categories of database refactoring with a new one:<ref name="access_refactoring_1">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік // Комп’ютерні науки, інформаційні технології та системи управління : Міжнародна науково-технічна конференція студентів, аспірантів та молодих вчених, 27–29 листопада 2019 р. – Івано-Франківськ : Прикарпатський національний університет ім. Василя Стефаника, 2019. – С. 20-21. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31516</ref>
	* Access Refactoring		* Access Refactoring
	::A change which relates to data access.		::A change which relates to data access.
	Methods of the Access Refactoring category<ref name="access_refactoring_2">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік, С. В. Грибков, В. В. Чобану // Наукові праці НУХТ. – Т. 26, № 2. – 2020. – С. 31–49. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31515</ref><ref name="access_refactoring_medium> ''Vladislav Struzik, PhD'' Refactoring: yesterday, today, tomorrow. URL: https://medium.com/@struzik/refactoring-yesterday-today-tomorrow-7fc8c845cfb1 </ref>: Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.		Methods of the Access Refactoring category:<ref name="access_refactoring_2">''Струзік, В. А.'' Категорія рефакторинг доступу / В. А. Струзік, С. В. Грибков, В. В. Чобану // Наукові праці НУХТ. – Т. 26, № 2. – 2020. – С. 31–49. URL: http://dspace.nuft.edu.ua/jspui/handle/123456789/31515</ref><ref name="access_refactoring_medium"> ''Vladislav Struzik, PhD'' Refactoring: yesterday, today, tomorrow. URL: https://medium.com/@struzik/refactoring-yesterday-today-tomorrow-7fc8c845cfb1 </ref> Change Authentication Attributes; Revoke Authorization Privileges; Grant Authorization Privileges; Extract Database Schema; Merge Database Schemas.

	==Process of database refactoring==		==Process of database refactoring==

93.188.34.224 at 22:26, 7 February 2023

2023-02-07T22:26:18Z

@@ Line 8: / Line 8: @@
 # To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.
-==Database refactorings==
+==Categories of Database Refactoring==
 ==Process of database refactoring==

Wqnvlz: Removed second person as per MOS:YOU; some cleanup

2020-12-25T19:39:18Z

Removed second person as per MOS:YOU; some cleanup

← Previous revision		Revision as of 19:39, 25 December 2020
Line 3:		Line 3:
	A database refactoring is conceptually more difficult than a [[code refactoring]]; code refactorings only need to maintain behavioral semantics while database refactorings also must maintain informational semantics.		A database refactoring is conceptually more difficult than a [[code refactoring]]; code refactorings only need to maintain behavioral semantics while database refactorings also must maintain informational semantics.

	~~You refactor a~~ database schema for one of several reasons:		A database schema is typically refactored for one of several reasons:
	# To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of ~~your~~ system.		# To develop the schema in an evolutionary manner in parallel with the evolutionary design of the rest of the system.
	# To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for [[database normalization]] of an existing production database, typically to "clean up" the design of the database.		# To fix design problems with an existing legacy database schema. Database refactorings are often motivated by the desire for [[database normalization]] of an existing production database, typically to "clean up" the design of the database.
	# To implement what would be a large (and potentially ~~risk~~) change as a series of small, low-risk changes.		# To implement what would be a large (and potentially risky) change as a series of small, low-risk changes.

	==Database refactorings==		==Database refactorings==
	Examples of database refactoring:		Examples of database refactoring:
	* Splitting an aggregate table into two different tables in the process of .		* Splitting an aggregate table into two different tables in the process of .{{Sentence fragment\|date=December 2020}}
	* Renaming an existing column to make its purpose clearer.		* Renaming an existing column to make its purpose clearer.
	* Combining two columns into a single one because they were being used for the same purpose.		* Combining two columns into a single one because they were being used for the same purpose.
	* Splitting an existing column into two or more columns ~~because~~ ~~the original column was being used for several purposes (so you~~ have ~~one column~~ ~~per~~ purpose).		* Splitting an existing column being used for multiple purposes into two or more columns that each have a single purpose.
	* Applying a common data format to a column so as to increase the consistency of the data.		* Applying a common data format to a column so as to increase the consistency of the data.
	* Common code refactorings (Rename Method, Introduce Variable, Rename Variable, and so on) to database code such as [[stored procedure]]s and [[Database trigger\|triggers]].		* Common code refactorings (Rename Method, Introduce Variable, Rename Variable, and so on) to database code such as [[stored procedure]]s and [[Database trigger\|triggers]].
Line 20:		Line 20:
	==Process of database refactoring==		==Process of database refactoring==
	The process of database refactoring is the act of applying database refactorings to evolve an existing database schema (database refactoring is a core practice of [[evolutionary database design]]). There are three considerations that need to be taken into account:		The process of database refactoring is the act of applying database refactorings to evolve an existing database schema (database refactoring is a core practice of [[evolutionary database design]]). There are three considerations that need to be taken into account:
	# How ~~to implement~~ a single refactoring		# How a single refactoring is implemented
	# How ~~to track/share~~ database refactorings ~~across~~ ~~your~~ ~~organization~~		# How database refactorings are tracked and shared within organizations
	# How ~~to apply~~ a series of database refactorings ~~to a database~~		# How a series of database refactorings are applied

	==See also==		==See also==

Jason Quinn: /* See also */ +Data migration

2020-10-19T14:13:53Z

← Previous revision		Revision as of 14:13, 19 October 2020
Line 26:		Line 26:
	==See also==		==See also==
	* [[Database testing]]		* [[Database testing]]
			* [[Data migration]]
	* [[Denormalization]]		* [[Denormalization]]
	* [[Refactoring]]		* [[Refactoring]]