Sandbox mode - Revision history

NWE at 09:27, 5 March 2026

2026-03-05T09:27:15Z

NWE at 09:26, 5 March 2026

2026-03-05T09:26:08Z

KNO at 12:07, 4 March 2015

2015-03-04T12:07:42Z

JKN at 11:44, 17 April 2013

2013-04-17T11:44:45Z

JKN at 11:44, 17 April 2013

2013-04-17T11:44:36Z

JKN: Created page with "In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage ..."

2013-04-17T11:30:28Z

Created page with "In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage ..."

New page

In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage when it comes to the management of large object models with lots of data. So the general recommendation is to use the Sandbox only during the customizing phase or for any task that requires rapid prototyping. Before providing productive data, the relevant classes should released, which basically means switching them to [[Live mode]].

← Older revision		Revision as of 09:27, 5 March 2026
Line 4:		Line 4:

	Use the [[Class Browser#Context menu\|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all its instances are in Sandbox mode as well.		Use the [[Class Browser#Context menu\|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all its instances are in Sandbox mode as well.
		+	==See also==
		+	* [[Dynamic_Live_Mode]]

	[[Category:UBIK\|Sandbox mode]]		[[Category:UBIK\|Sandbox mode]]

@@ Line 1: / Line 1: @@
 In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage when it comes to the management of large object models with lots of data. So the general recommendation is to use the Sandbox only during the customizing phase or for any task that requires rapid prototyping. Before providing productive data, the relevant classes should released, which basically means switching them to [[Live mode]].
 Use the [[Class Browser#Context menu|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all its instances are in Sandbox mode as well.
-[[Category:UBIK]]
+[[Category:UBIK|Sandbox mode]]

← Older revision		Revision as of 12:07, 4 March 2015
Line 2:		Line 2:

	Use the [[Class Browser#Context menu\|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all its instances are in Sandbox mode as well.		Use the [[Class Browser#Context menu\|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all its instances are in Sandbox mode as well.
		+
		+	[[Category:UBIK]]

← Older revision		Revision as of 11:44, 17 April 2013
Line 1:		Line 1:
	In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage when it comes to the management of large object models with lots of data. So the general recommendation is to use the Sandbox only during the customizing phase or for any task that requires rapid prototyping. Before providing productive data, the relevant classes should released, which basically means switching them to [[Live mode]].		In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage when it comes to the management of large object models with lots of data. So the general recommendation is to use the Sandbox only during the customizing phase or for any task that requires rapid prototyping. Before providing productive data, the relevant classes should released, which basically means switching them to [[Live mode]].

−	Use the [[Class Browser#Context menu\|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all instances are in Sandbox mode as well.	+	Use the [[Class Browser#Context menu\|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all its instances are in Sandbox mode as well.

← Older revision		Revision as of 11:44, 17 April 2013
Line 1:		Line 1:
	In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage when it comes to the management of large object models with lots of data. So the general recommendation is to use the Sandbox only during the customizing phase or for any task that requires rapid prototyping. Before providing productive data, the relevant classes should released, which basically means switching them to [[Live mode]].		In Sandbox mode, {{UBIK}} holds its data in a relatively flat table structure in the database. While this is very nice in terms of flexibility, it is certainly a disadvantage when it comes to the management of large object models with lots of data. So the general recommendation is to use the Sandbox only during the customizing phase or for any task that requires rapid prototyping. Before providing productive data, the relevant classes should released, which basically means switching them to [[Live mode]].
		+
		+	Use the [[Class Browser#Context menu\|Class Browser's]] context menu to switch the mode of a [[MetaClass]]. Once a MetaClass is switched into Sandbox mode, all instances are in Sandbox mode as well.