SqlCVS - Revision history

Marie.o: /* Creating the "MasterUsers" database */

2011-10-06T18:59:11Z

Creating the "MasterUsers" database

←Older revision		Revision as of 18:59, 6 October 2011
Line 105:		Line 105:
	'20071103193538','',0,1,NULL,NULL,NULL,0,'2007-11-03 18:41:22',NULL);		'20071103193538','',0,1,NULL,NULL,NULL,0,'2007-11-03 18:41:22',NULL);
	</pre>		</pre>

			Make sure to set sqlCvsAdmin to 1 for people who need to commit stuff to schema.

	=== Setting up a chroot ===		=== Setting up a chroot ===

Marie.o: /* Special fields */

2009-12-02T15:39:55Z

Special fields

←Older revision		Revision as of 15:39, 2 December 2009
Line 561:		Line 561:
	\| psc_frozen \| tinyint(1) \| YES \| \| 0 \| \| # frozen rows cant be changed		\| psc_frozen \| tinyint(1) \| YES \| \| 0 \| \| # frozen rows cant be changed
	\| psc_mod \| timestamp \| YES \| \| CURRENT_TIMESTAMP \| \| # last modification of the row		\| psc_mod \| timestamp \| YES \| \| CURRENT_TIMESTAMP \| \| # last modification of the row
	\| psc_restrict \| int(11) \| YES \| \| NULL \| \|		\| psc_restrict \| int(11) \| YES \| \| NULL \| \| # if != NULL do not update clients
	</pre>		</pre>

	== Repository ==		== Repository ==
	=== Repository Settings Table "psc_<repo>_repset" ===		=== Repository Settings Table "psc_<repo>_repset" ===

Marie.o: /* Repository Tables Table "psctables" */ Note on the filter field in psctables

2009-05-19T13:43:52Z

Repository Tables Table "psc_<repo>_tables": Note on the filter field in psc_<repo>_tables

←Older revision		Revision as of 13:43, 19 May 2009
Line 593:		Line 593:
	\| PK_psc_dce_tables \| int(11) \| NO \| PRI \| NULL \| auto_increment \|		\| PK_psc_dce_tables \| int(11) \| NO \| PRI \| NULL \| auto_increment \|
	\| Tablename \| varchar(60) \| NO \| \| \| \|		\| Tablename \| varchar(60) \| NO \| \| \| \|
	\| filter \| varchar(255) \| YES \| \| NULL \| \| ?		\| filter \| varchar(255) \| YES \| \| NULL \| \| ~~~ This seems to be the filter for what gets exported, i.e. where 0 means, no records are exported.
	\| frozen \| tinyint(1) \| NO \| \| 0 \| \| if true no changes to that table are accepted		\| frozen \| tinyint(1) \| NO \| \| 0 \| \| if true no changes to that table are accepted
	\| anonymous \| tinyint(1) \| NO \| \| 0 \| \| if true anonymous~anonymous can check in to this table		\| anonymous \| tinyint(1) \| NO \| \| 0 \| \| if true anonymous~anonymous can check in to this table
Line 600:		Line 600:
	+-------------------+--------------+------+-----+---------+----------------+		+-------------------+--------------+------+-----+---------+----------------+
	</pre>		</pre>

	=== Schema Table "psc_<repo>_schema" ===		=== Schema Table "psc_<repo>_schema" ===
	This table holds the schema changes for tables in a repository. Example:		This table holds the schema changes for tables in a repository. Example:

Marie.o: modified sample INSERT statement to use md5 function for password

2009-04-04T10:10:43Z

modified sample INSERT statement to use md5 function for password

←Older revision		Revision as of 10:10, 4 April 2009
Line 102:		Line 102:
	A sample user could look like this:		A sample user could look like this:
	<pre>		<pre>
	INSERT INTO `MasterUsers` VALUES (1,'000001','C06','Users','hari','~~c13b52531693f788a16fd56c35a47f04~~',0,'hari@vt100.at',		INSERT INTO `MasterUsers` VALUES (1,'000001','C06','Users','hari',md5('sUperSecreTpassword'),0,'hari@vt100.at',
	'20071103193538','',0,1,NULL,NULL,NULL,0,'2007-11-03 18:41:22',NULL);		'20071103193538','',0,1,NULL,NULL,NULL,0,'2007-11-03 18:41:22',NULL);
	</pre>		</pre>

Marie.o: /* Managing users */

2008-10-21T17:15:21Z

Managing users

←Older revision		Revision as of 17:15, 21 October 2008
Line 220:		Line 220:
	=== Managing users ===		=== Managing users ===

	~~The~~ users are ~~stored~~ in the ~~db "~~MasterUsers" table "MasterUsers". There is a Web-Interface at http://svn.plutohome.com/pluto/trunk/web/masterusers-site. But it seems to be only used for kinda "http-rpc" and depends on multiple databases (mantis, phpbb, ...). Some tweaks give us a simple "add user" interface. The password has to be specified as md5 hash.		Currently users are managed manually in the MasterUsers table.

	NOTE: there is a new web interface at http://svn.charonmedia.org/svn/trunk/web/sqlcvsweb. It includes add user functionality.		NOTE: there is a new web interface at http://svn.charonmedia.org/svn/trunk/web/sqlcvsweb. It includes add user functionality.

Hari: /* sqlCVS data modell */

2008-08-13T20:15:50Z

sqlCVS data modell

←Older revision		Revision as of 20:15, 13 August 2008
Line 470:		Line 470:

	= sqlCVS data modell =		= sqlCVS data modell =
	== Detailed psc table description		== Detailed psc table description ==
	[[What_do_the_psc_tables_do%3F]]		[[What_do_the_psc_tables_do%3F]]
	== Batches ==		== Batches ==

Hari: /* sqlCVS data modell */

2008-08-13T20:15:23Z

sqlCVS data modell

←Older revision		Revision as of 20:15, 13 August 2008
Line 470:		Line 470:

	= sqlCVS data modell =		= sqlCVS data modell =
			== Detailed psc table description
			[[What_do_the_psc_tables_do%3F]]
	== Batches ==		== Batches ==
	=== Header Table "psc_<repo>_bathdr" ===		=== Header Table "psc_<repo>_bathdr" ===

Danielk: /* Introduction */

2008-03-19T15:21:18Z

Introduction

←Older revision		Revision as of 15:21, 19 March 2008
Line 1:		Line 1:
	{\| align="right"		{\| align="right"
	\| __TOC__		\| __TOC__
	\|}		\|}
Line 5:		Line 5:

	= Introduction =		= Introduction =

			This article describes how to use sqlCVS in general. There is a separate article on committing SQL into the linuxmce sqlCVS repository, please see the [[LinuxMCEsqlCVScommitProcedure\|LinuxMCE sqlCVS commit process]] for information on how to share a new IR code or other improvement with the community.

	== Sample Uses ==		== Sample Uses ==

Line 24:		Line 27:

	sqlCVS is completely transparent. The software that uses the database does not need to be aware of sqlCVS. The only database consideration is that the field names must follow a logical naming convention so sqlCVS can determine what are foreign keys.		sqlCVS is completely transparent. The software that uses the database does not need to be aware of sqlCVS. The only database consideration is that the field names must follow a logical naming convention so sqlCVS can determine what are foreign keys.

	= Users Manual =		= Users Manual =
	== Overview ==		== Overview ==

Hari at 11:45, 28 November 2007

2007-11-28T11:45:00Z

←Older revision		Revision as of 11:45, 28 November 2007
Line 616:		Line 616:
	+-------------------------+-------------------------------------------------------------------------------------------------------------------+		+-------------------------+-------------------------------------------------------------------------------------------------------------------+
	</pre>		</pre>

	= Tutorial for new repositories =		= Tutorial for new repositories =

Hari: /* Schema Table "psc__schema" */

2007-11-28T11:42:41Z

Schema Table "psc_<repo>_schema"

←Older revision		Revision as of 11:42, 28 November 2007
Line 616:		Line 616:
	+-------------------------+-------------------------------------------------------------------------------------------------------------------+		+-------------------------+-------------------------------------------------------------------------------------------------------------------+
	</pre>		</pre>
			= Tutorial for new repositories =

SqlCVS - Revision history

Marie.o: /* Creating the "MasterUsers" database */

Marie.o: /* Special fields */

Marie.o: /* Repository Tables Table "psc__tables" */ Note on the filter field in psc__tables

Marie.o: modified sample INSERT statement to use md5 function for password

Marie.o: /* Managing users */

Hari: /* sqlCVS data modell */

Hari: /* sqlCVS data modell */

Danielk: /* Introduction */

Hari at 11:45, 28 November 2007

Hari: /* Schema Table "psc__schema" */

Marie.o: /* Repository Tables Table "psctables" */ Note on the filter field in psctables