Production DataBases : mysql - Revision history

Sertonix: fix redirect until deleted

2023-11-10T11:25:50Z

fix redirect until deleted

← Older revision		Revision as of 11:25, 10 November 2023
Line 1:		Line 1:
			#REDIRECT [[MySQL]]

	{{Delete\|Contents merged into MySQL, nothing links here.}}		{{Delete\|Contents merged into MySQL, nothing links here.}}

	~~#REDIRECT [[MySQL]]~~

2023-08-28T04:34:46Z

RfD

← Older revision		Revision as of 04:34, 28 August 2023
Line 1:		Line 1:
			{{Delete\|Contents merged into MySQL, nothing links here.}}

	#REDIRECT [[MySQL]]		#REDIRECT [[MySQL]]

2023-08-28T04:28:28Z

Merged into MySQL. Preparation for RfD: WIP.

2023-08-28T04:19:41Z

Fixed the typo I just made.

← Older revision		Revision as of 04:19, 28 August 2023
Line 1:		Line 1:
	{{merge\|~~MySQLl~~}}		{{merge\|MySQL}}
	[https://mariadb.org/ MariaDB] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.		[https://mariadb.org/ MariaDB] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.

2023-08-28T04:19:18Z

Fixed double redirect / merge proposal.

← Older revision		Revision as of 04:19, 28 August 2023
Line 1:		Line 1:
	{{merge\|~~mysql~~}}		{{merge\|MySQLl}}
	[https://mariadb.org/ MariaDB] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.		[https://mariadb.org/ MariaDB] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.

2023-03-24T04:55:01Z

Technical: Removed dead links

← Older revision		Revision as of 04:55, 24 March 2023
Line 253:		Line 253:
	* [[MariaDB\|MariaDB wiki page]]		* [[MariaDB\|MariaDB wiki page]]
	* [[Production LAMP system: Lighttpd + PHP + MySQL]]		* [[Production LAMP system: Lighttpd + PHP + MySQL]]
	* [[Alpine newbie developer]]

	[[Category:Newbie]]		[[Category:Newbie]]

2022-09-06T20:18:13Z

← Older revision		Revision as of 20:18, 6 September 2022
Line 1:		Line 1:
			{{merge\|mysql}}
	[https://mariadb.org/ MariaDB] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.		[https://mariadb.org/ MariaDB] is a community-developed fork of the MySQL relational database management system intended to remain free under the GNU GPL. It is notable for being led by the original developers of MySQL, who forked it due to concerns over its acquisition by Oracle.

2021-12-31T15:54:01Z

File system notes about the databases managed

← Older revision		Revision as of 15:54, 31 December 2021
Line 218:		Line 218:
	== File system notes about the databases managed ==		== File system notes about the databases managed ==

	'''~~BTRFS~~ Notes'''		'''Btrfs Notes'''

	If the database (in <code>/var/lib/mysql</code>) resides on a [[~~BTRFS~~\|btrfs]] file system, you should consider disabling '''Copy-on-Write''' for the directory before creating any database (schemes), after initialization you can enabled again. But .. on every database creation (scheme creation), you must disabled again, to avoid corrupted data.		If the database (in <code>/var/lib/mysql</code>) resides on a [[Btrfs\|btrfs]] file system, you should consider disabling '''Copy-on-Write''' for the directory before creating any database (schemes), after initialization you can enabled again. But .. on every database creation (scheme creation), you must disabled again, to avoid corrupted data.

	'''ZFS Bock sizes'''		'''ZFS Bock sizes'''

2021-12-31T14:20:50Z

File system notes about the databases managed: add reference to btrfs page

← Older revision		Revision as of 14:20, 31 December 2021
Line 220:		Line 220:
	'''BTRFS Notes'''		'''BTRFS Notes'''

	If the database (in <code>/var/lib/mysql</code>) resides on a ~~Btrfs~~ file system, you should consider disabling '''Copy-on-Write''' for the directory before creating any database (schemes), after initialization you can enabled again. But .. on every database creation (scheme creation), you must disabled again, to avoid corrupted data.		If the database (in <code>/var/lib/mysql</code>) resides on a [[BTRFS\|btrfs]] file system, you should consider disabling '''Copy-on-Write''' for the directory before creating any database (schemes), after initialization you can enabled again. But .. on every database creation (scheme creation), you must disabled again, to avoid corrupted data.

	'''ZFS Bock sizes'''		'''ZFS Bock sizes'''

2021-12-14T19:41:14Z

See Also: Removed wikilink to non-existent article.

← Older revision		Revision as of 19:41, 14 December 2021
Line 253:		Line 253:
	* [[Production LAMP system: Lighttpd + PHP + MySQL]]		* [[Production LAMP system: Lighttpd + PHP + MySQL]]
	* [[Alpine newbie developer]]		* [[Alpine newbie developer]]
	* [[Alpine newbie lammers]]

	[[Category:Newbie]]		[[Category:Newbie]]