Development:XMLDB problems - Revision history

Cxjohnson: grammar / spelling corrections

2009-04-02T20:42:49Z

grammar / spelling corrections

← Older revision		Revision as of 20:42, 2 April 2009
Line 250:		Line 250:
	('''Status:''' Closed - '''Severity:''' Critical - '''Bug:''' not defined)		('''Status:''' Closed - '''Severity:''' Critical - '''Bug:''' not defined)

	Every DB ~~use it's~~ own approach about using table and columns aliases using the '''AS''' keyword. This is the summary:		Every DB uses its own approach about using table and columns aliases using the '''AS''' keyword. This is the summary:

	* '''MySQL''': supports AS in tables, supports AS in fields.		* '''MySQL''': supports AS in tables, supports AS in fields.

Tsala: cat edit

2007-06-18T10:11:34Z

cat edit

← Older revision		Revision as of 10:11, 18 June 2007
Line 271:		Line 271:
	* [[XMLDB preliminary notes]]: Some preliminary notes when problems were initially detected and briefly noted.		* [[XMLDB preliminary notes]]: Some preliminary notes when problems were initially detected and briefly noted.

	~~[[Category:Developer]]~~
	[[Category:XMLDB]]		[[Category:XMLDB]]

Moquist at 01:52, 1 June 2007

2007-06-01T01:52:59Z

← Older revision		Revision as of 01:52, 1 June 2007
Line 3:		Line 3:
	Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').		Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').

	Of course, ~~fell~~ free to use the [http://moodle.org/bugs Bug Tracker] to follow the daily evolution of each one of these problems by adding one link inside each section pointing to the proper bug.		Of course, feel free to use the [http://moodle.org/bugs Bug Tracker] to follow the daily evolution of each one of these problems by adding one link inside each section pointing to the proper bug.

	Prior to change the status from ''''Decided'''' to ''''Work in progress'''' the corresponding page of the [[XMLDB Roadmap\|roadmap]] must be modified, including all the actions/steps needed to solve the problem. Obviously, at the end, the expected status for each section is ''''Closed''''.		Prior to change the status from ''''Decided'''' to ''''Work in progress'''' the corresponding page of the [[XMLDB Roadmap\|roadmap]] must be modified, including all the actions/steps needed to solve the problem. Obviously, at the end, the expected status for each section is ''''Closed''''.

Stronk7 at 16:49, 28 February 2007

2007-02-28T16:49:53Z

← Older revision		Revision as of 16:49, 28 February 2007
Line 1:		Line 1:
	~~[[Development:XML database schema\|XML database schema]] >~~ [[Development:XMLDB Documentation\|Documentation]] > XMLDB Problems		[[Development:XMLDB Documentation\|XMLDB Documentation]] > XMLDB Problems
	----		----
	Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').		Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').

Stronk7 at 16:35, 28 February 2007

2007-02-28T16:35:43Z

← Older revision		Revision as of 16:35, 28 February 2007
Line 1:		Line 1:
	[[Development:XML database schema\|XML database schema]] > XMLDB Problems		[[Development:XML database schema\|XML database schema]] > [[Development:XMLDB Documentation\|Documentation]] > XMLDB Problems
	----		----
	Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').		Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').

Stronk7: /* NOT NULL fields using a DEFAULT '' clause */

2007-02-04T00:02:59Z

NOT NULL fields using a DEFAULT <nowiki>''</nowiki> clause

← Older revision		Revision as of 00:02, 4 February 2007
Line 52:		Line 52:
	After 1.7, we should start to modify MySQL, PostgreSQL and MSSQL implementation to use the same (correct) field definition (nullable columns) with more time to change/test/fix everything, progressively moving NOT NULL stuff to NULL if it's really nullable, dropping all those empty defaults.		After 1.7, we should start to modify MySQL, PostgreSQL and MSSQL implementation to use the same (correct) field definition (nullable columns) with more time to change/test/fix everything, progressively moving NOT NULL stuff to NULL if it's really nullable, dropping all those empty defaults.

	'''Updated:''' For 1.7 we have started the migration of TEXT fields that, being logic, can contain no data, from NOT NULL to NULL, while we'll maintain VARCHAR fields as explained above. This will give us a real idea of the impact of such change across Moodle code while will produce one better (real) DB Schema. After 1.7, all the rest of VARCHAR fields should follow the same process, being transformed from NOT NULL to NULL if the application logic says that they can have no contents. Then, all those empty ('') defaults will be out. Definitively! For Oracle we are inserting/updating 1 whitespace in all the NOT NULL, default '' fields and converting them back in all the get_xxx() DML functions (this is called in code: '''Oracle dirty hack'''). Hopefully will be out in ~~1.8~~.		'''Updated:''' For 1.7 we have started the migration of TEXT fields that, being logic, can contain no data, from NOT NULL to NULL, while we'll maintain VARCHAR fields as explained above. This will give us a real idea of the impact of such change across Moodle code while will produce one better (real) DB Schema. After 1.7, all the rest of VARCHAR fields should follow the same process, being transformed from NOT NULL to NULL if the application logic says that they can have no contents. Then, all those empty ('') defaults will be out. Definitively! For Oracle we are inserting/updating 1 whitespace in all the NOT NULL, default '' fields and converting them back in all the get_xxx() DML functions (this is called in code: '''Oracle dirty hack'''). Hopefully will be out in some releases.

	Here you'll find a list of TEXT fields transformed from NOT NULL to NULL (in the 1.6 --> 1.7) upgrade:		Here you'll find a list of TEXT fields transformed from NOT NULL to NULL (in the 1.6 --> 1.7) upgrade:

SamuliK: Just testing link namespace fixes.

2007-02-01T05:46:50Z

Just testing link namespace fixes.

← Older revision		Revision as of 05:46, 1 February 2007
Line 1:		Line 1:
	[[XML database schema]] > XMLDB Problems		[[Development:XML database schema\|XML database schema]] > XMLDB Problems
	----		----
	Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').		Every section on this page will show important problems present in the adoption of the new database layer planned for 1.7. Each section will define the problem, its impact and, when available, its solution. Every section will include one line containing its status (''''Open'''', ''''Decided''', ''''Work in progress'''', ''''Finished'''', ''''Tested'''' and ''''Closed'''').

Zacharydl: /* MSSQL, PHP, UTF-8 and UCS-2 */

2006-12-21T20:18:49Z

MSSQL, PHP, UTF-8 and UCS-2

← Older revision		Revision as of 20:18, 21 December 2006
Line 123:		Line 123:
	And finally, they exist! We've found two products ('''OpenSource, of course''') that fulfil all the requirements detailed above. Both perform the automatic conversion between UTF-8 and UCS-2, replace the standard php_mssql library so we'll continue using the well supported mssql ADOdb driver and are cross-platform. Anything more, nah, here they are:		And finally, they exist! We've found two products ('''OpenSource, of course''') that fulfil all the requirements detailed above. Both perform the automatic conversion between UTF-8 and UCS-2, replace the standard php_mssql library so we'll continue using the well supported mssql ADOdb driver and are cross-platform. Anything more, nah, here they are:

	* '''[http://www.freetds.org/ ~~FreeDTS~~]''': This a 100% client product that it's based in the [[Wikipedia:Tabular_Data_Stream\|Tabular Data Protocol]] supported both SQL*Server and Sybase. We have compiled and used it both under Linux and MacOS X without problems and with one minimal configuration it replaces the standard php_mssql extension smoothly. The documentation says it works also under Win32 systems but we haven't tried it there. Tons of reports in Internet talk about it as a reliable solution.		* '''[http://www.freetds.org/ FreeTDS]''': This a 100% client product that it's based in the [[Wikipedia:Tabular_Data_Stream\|Tabular Data Protocol]] supported both SQL*Server and Sybase. We have compiled and used it both under Linux and MacOS X without problems and with one minimal configuration it replaces the standard php_mssql extension smoothly. The documentation says it works also under Win32 systems but we haven't tried it there. Tons of reports in Internet talk about it as a reliable solution.
	* '''[http://odbtp.sourceforge.net/ ODBTP]''': This is another protocol, Open Database Transport Protocol, that allows to connect virtually to any Win32 DB server. It requires both one client installation and one service to be installed in one Win32 machine (to act as bridge between the client and the DB, via ODBC). The client part is available for Linux and MacOS X (not tested) and also implements one replacement for the standard php_mssql extension. The service part is obviously, available only for Win32. After a minimal configuration it works perfectly and it's announced as reliable for critical missions.		* '''[http://odbtp.sourceforge.net/ ODBTP]''': This is another protocol, Open Database Transport Protocol, that allows to connect virtually to any Win32 DB server. It requires both one client installation and one service to be installed in one Win32 machine (to act as bridge between the client and the DB, via ODBC). The client part is available for Linux and MacOS X (not tested) and also implements one replacement for the standard php_mssql extension. The service part is obviously, available only for Win32. After a minimal configuration it works perfectly and it's announced as reliable for critical missions.

Stronk7: /* NOT NULL fields using a DEFAULT '' clause */

2006-11-05T09:27:03Z

NOT NULL fields using a DEFAULT <nowiki>''</nowiki> clause

← Older revision		Revision as of 09:27, 5 November 2006
Line 67:		Line 67:
	Here you'll find a list of TEXT fields transformed from NOT NULL to NULL (in the 1.7 --> 1.8) upgrade:		Here you'll find a list of TEXT fields transformed from NOT NULL to NULL (in the 1.7 --> 1.8) upgrade:

	* ~~(empty yet)~~		* Follow [http://tracker.moodle.org/browse/MDL-7354 this report in the Tracker]

	== Indexes on TEXT columns ==		== Indexes on TEXT columns ==

Stronk7: /* NOT NULL fields using a DEFAULT '' clause */

2006-10-22T23:28:42Z

NOT NULL fields using a DEFAULT <nowiki>''</nowiki> clause

← Older revision		Revision as of 23:28, 22 October 2006
Line 52:		Line 52:
	After 1.7, we should start to modify MySQL, PostgreSQL and MSSQL implementation to use the same (correct) field definition (nullable columns) with more time to change/test/fix everything, progressively moving NOT NULL stuff to NULL if it's really nullable, dropping all those empty defaults.		After 1.7, we should start to modify MySQL, PostgreSQL and MSSQL implementation to use the same (correct) field definition (nullable columns) with more time to change/test/fix everything, progressively moving NOT NULL stuff to NULL if it's really nullable, dropping all those empty defaults.

	'''Updated:''' For 1.7 we have started the migration of TEXT fields that, being logic, can contain no data, from NOT NULL to NULL, while we'll maintain VARCHAR fields as explained above. This will give us a real idea of the impact of such change across Moodle code while will produce one better (real) DB Schema. After 1.7, all the rest of VARCHAR fields should follow the same process, being transformed from NOT NULL to NULL if the application logic says that they can have no contents. Then, all those empty ('') defaults will be out. Definitively!		'''Updated:''' For 1.7 we have started the migration of TEXT fields that, being logic, can contain no data, from NOT NULL to NULL, while we'll maintain VARCHAR fields as explained above. This will give us a real idea of the impact of such change across Moodle code while will produce one better (real) DB Schema. After 1.7, all the rest of VARCHAR fields should follow the same process, being transformed from NOT NULL to NULL if the application logic says that they can have no contents. Then, all those empty ('') defaults will be out. Definitively! For Oracle we are inserting/updating 1 whitespace in all the NOT NULL, default '' fields and converting them back in all the get_xxx() DML functions (this is called in code: '''Oracle dirty hack'''). Hopefully will be out in 1.8.

	Here you'll find a list of TEXT fields transformed from NOT NULL to NULL (in the 1.6 --> 1.7) upgrade:		Here you'll find a list of TEXT fields transformed from NOT NULL to NULL (in the 1.6 --> 1.7) upgrade: