SqlCVS - Managing schema changes - Revision history

Phenigma at 23:16, 20 January 2016

2016-01-20T23:16:54Z

←Older revision		Revision as of 23:16, 20 January 2016
Line 1:		Line 1:
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	Modifying existing tables in sqlCVS is a multistep process which involves manually executing stuff on the sqlCVS main server (schema.linuxmce.org as of this writing). The current master database is main_sqlcvs_utf8.		Modifying existing tables in sqlCVS is a multistep process which involves manually executing stuff on the sqlCVS main server (schema.linuxmce.org as of this writing). The current master database is main_sqlcvs_utf8. You must remember to perform a new sql2cpp run after re-importing the databases from schema and commit any changes to the database libraries. This will usually require a complete rebuild of all LinuxMCE packages.

	= On the main sqlCVS server =		= On the main sqlCVS server =

Phenigma at 11:30, 20 April 2014

2014-04-20T11:30:39Z

←Older revision		Revision as of 11:30, 20 April 2014
Line 17:		Line 17:
	= On the local system =		= On the local system =
	To update the schema on our system, we need to run the update command locally (or do this through webadmin, which is not possible for the 'local' repo)		To update the schema on our system, we need to run the update command locally (or do this through webadmin, which is not possible for the 'local' repo)
	/usr/pluto/bin/sqlCVS -H schema.linuxmce.org -R 3999 -U anonymous~~~anonymous~~ -r local update		/usr/pluto/bin/sqlCVS -H schema.linuxmce.org -R 3999 -U anonymous~nopass -r local update

	= Notes =		= Notes =
	If anyone knows of a simpler approach, please amend. Thanks.		If anyone knows of a simpler approach, please amend. Thanks.

Phenigma: /* On the local system */

2014-04-20T03:31:53Z

On the local system

←Older revision		Revision as of 03:31, 20 April 2014
Line 16:		Line 16:

	= On the local system =		= On the local system =
	To update the schema on our system, we need to run the update command locally (or do this through webadmin)		To update the schema on our system, we need to run the update command locally (or do this through webadmin, which is not possible for the 'local' repo)
	/usr/pluto/bin/sqlCVS -H schema.linuxmce.org -R 3999 -U anonymous~anonymous -r local update		/usr/pluto/bin/sqlCVS -H schema.linuxmce.org -R 3999 -U anonymous~anonymous -r local update

	= Notes =		= Notes =
	If anyone knows of a simpler approach, please amend. Thanks.		If anyone knows of a simpler approach, please amend. Thanks.

Phenigma: /* On the local system */

2014-04-20T03:31:05Z

On the local system

←Older revision		Revision as of 03:31, 20 April 2014
Line 16:		Line 16:

	= On the local system =		= On the local system =
	To update the schema on our system, we need to run the ~~dump~~ command locally		To update the schema on our system, we need to run the update command locally (or do this through webadmin)
	/usr/pluto/bin/sqlCVS -H schema.linuxmce.org -R 3999 -r local ~~dump~~		/usr/pluto/bin/sqlCVS -H schema.linuxmce.org -R 3999 -U anonymous~anonymous -r local update

	= Notes =		= Notes =
	If anyone knows of a simpler approach, please amend. Thanks.		If anyone knows of a simpler approach, please amend. Thanks.

Phenigma: /* Update the psc__repset table */

2014-04-20T01:50:15Z

Update the psc__repset table

←Older revision		Revision as of 01:50, 20 April 2014
Line 8:		Line 8:

	== Update the psc_<repo>_repset table==		== Update the psc_<repo>_repset table==
	After adding the above alter statement to the schema, we need to update table rep_set with the latest ~~psc_id~~ created by the above statement		After adding the above alter statement to the schema, we need to update table rep_set with the latest PK_psc_local_schema created by the above statement
	UPDATE psc_local_repset SET Value=(Select max(PK_psc_local_schema) From psc_local_schema);		UPDATE psc_local_repset SET Value=(Select max(PK_psc_local_schema) From psc_local_schema);

Phenigma: /* Update the psc__repset table */

2014-04-20T01:49:55Z

Update the psc__repset table

←Older revision		Revision as of 01:49, 20 April 2014
Line 9:		Line 9:
	== Update the psc_<repo>_repset table==		== Update the psc_<repo>_repset table==
	After adding the above alter statement to the schema, we need to update table rep_set with the latest psc_id created by the above statement		After adding the above alter statement to the schema, we need to update table rep_set with the latest psc_id created by the above statement
	UPDATE psc_local_repset SET Value=(Select max(~~psc_id~~) From psc_local_schema);		UPDATE psc_local_repset SET Value=(Select max(PK_psc_local_schema) From psc_local_schema);

	== Modifying the actual table ==		== Modifying the actual table ==

Phenigma at 01:43, 20 April 2014

2014-04-20T01:43:25Z

←Older revision		Revision as of 01:43, 20 April 2014
Line 1:		Line 1:
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	Modifying existing tables in sqlCVS is a multistep process which involves manually executing stuff on the sqlCVS main server (schema.linuxmce.org as of this writing). The current master database is ~~main_sqlcvs~~.		Modifying existing tables in sqlCVS is a multistep process which involves manually executing stuff on the sqlCVS main server (schema.linuxmce.org as of this writing). The current master database is main_sqlcvs_utf8.

	= On the main sqlCVS server =		= On the main sqlCVS server =
Line 12:		Line 12:

	== Modifying the actual table ==		== Modifying the actual table ==
	Now we modify the actual table, by executing the ALTER TABLE command in the ~~main_sqlcvs~~ database		Now we modify the actual table, by executing the ALTER TABLE command in the main_sqlcvs_utf8 database
	ALTER TABLE `CommandGroup` ADD `FK_Text` INT(11) DEFAULT NULL AFTER `TemplateParm2`;		ALTER TABLE `CommandGroup` ADD `FK_Text` INT(11) DEFAULT NULL AFTER `TemplateParm2`;

Phenigma: Phenigma moved page SqlCVS-Modifying table structure to SqlCVS - Managing schema changes: referenced from other page this way.

2014-04-17T23:55:40Z

Phenigma moved page SqlCVS-Modifying table structure to SqlCVS - Managing schema changes: referenced from other page this way.

←Older revision	Revision as of 23:55, 17 April 2014
(No difference)

Marie.o: categorized

2009-10-28T18:02:51Z

categorized

←Older revision		Revision as of 18:02, 28 October 2009
Line 1:		Line 1:
			[[Category: Programmer's Guide]]
	Modifying existing tables in sqlCVS is a multistep process which involves manually executing stuff on the sqlCVS main server (schema.linuxmce.org as of this writing). The current master database is main_sqlcvs.		Modifying existing tables in sqlCVS is a multistep process which involves manually executing stuff on the sqlCVS main server (schema.linuxmce.org as of this writing). The current master database is main_sqlcvs.

Marie.o: Initial article on how to modify database structure which is under the control of sqlCVS

2009-10-28T17:31:10Z

Initial article on how to modify database structure which is under the control of sqlCVS

New page

Modifying existing tables in sqlCVS is a multistep process which involves manually executing stuff on the sqlCVS main server (schema.linuxmce.org as of this writing). The current master database is main_sqlcvs.

= On the main sqlCVS server =
== Add the modification statement to psc_<repo>_schema==
For example, to add a new field FK_Text to the CommandGroup table in the local repository, the command is
insert into psc_local_schema set Value= "ALTER TABLE `CommandGroup` ADD `FK_Text` INT(11) DEFAULT NULL AFTER `TemplateParm2`";

== Update the psc_<repo>_repset table==
After adding the above alter statement to the schema, we need to update table rep_set with the latest psc_id created by the above statement
UPDATE psc_local_repset SET Value=(Select max(psc_id) From psc_local_schema);

== Modifying the actual table ==
Now we modify the actual table, by executing the ALTER TABLE command in the main_sqlcvs database
ALTER TABLE `CommandGroup` ADD `FK_Text` INT(11) DEFAULT NULL AFTER `TemplateParm2`;

= On the local system =
To update the schema on our system, we need to run the dump command locally
/usr/pluto/bin/sqlCVS -H schema.linuxmce.org -R 3999 -r local dump

= Notes =
If anyone knows of a simpler approach, please amend. Thanks.