Tutorial: Database Development - Revision history

Teemu Mätäsniemi: /* Asynchronous read with a SyncListener */

2013-12-05T17:20:52Z

Asynchronous read with a SyncListener

@@ Line 132: / Line 132: @@
 </pre>
 Here the listener updates the label when the name changes. The method isDisposed() controls lifecycle of the listener, and here when the label is disposed, the listener is released and it stops updating the label.
 ==Resources==

2012-09-03T12:05:56Z

Explicit clustering

← Older revision		Revision as of 12:05, 3 September 2012
Line 205:		Line 205:
	public void perform(WriteGraph graph) throws DatabaseException {		public void perform(WriteGraph graph) throws DatabaseException {
	Layer0 l0 = Layer0.getInstance(graph);		Layer0 l0 = Layer0.getInstance(graph);
			Resource oldClusterSet = graph.setClusterSet4NewResource(l0.InstanceOf);
	try {		try {
	graph.~~newClusterSet~~(l0.InstanceOf);		Resource newResource = graph.newResource();
	} ~~catch (ClusterSetExistException e)~~ {		graph.claim(newResource, l0.InstanceOf, null, l0.Entity);
	~~// Cluster set exits, no problem~~.		} finally {
			graph.setClusterSet4NewResource(oldClusterSet);
	}		}
	~~Resource newResource = graph.newResource(l0.InstanceOf);~~
	~~graph.claim(newResource, l0.InstanceOf, null, l0.Entity);~~
	}		}
	});		});

2012-09-03T11:25:16Z

Setting Literals

← Older revision		Revision as of 11:25, 3 September 2012
Line 177:		Line 177:

	=Writing the database=		=Writing the database=
			==Explicit clustering==

			Here we show how you can influence the way resources are grouped by the underlying implemention. You can significantly improve the dynamic behaviour of the database by grouping resources that are likely to be referenced in the same context/operation.

			<pre>
			try {
			session.syncRequest(new WriteRequest() {
			@Override
			public void perform(WriteGraph graph) throws DatabaseException {
			Layer0 l0 = Layer0.getInstance(graph);
			try {
			graph.newClusterSet(l0.InstanceOf);
			} catch (ClusterSetExistException e) {
			// Cluster set exits, no problem.
			}
			Resource newResource = graph.newResource(l0.InstanceOf);
			graph.claim(newResource, l0.InstanceOf, null, l0.Entity);
			}
			});
			</pre>

			Here is the same effect with setting a default for newResource method.

			<pre>
			session.syncRequest(new WriteRequest() {
			@Override
			public void perform(WriteGraph graph) throws DatabaseException {
			Layer0 l0 = Layer0.getInstance(graph);
			try {
			graph.newClusterSet(l0.InstanceOf);
			} catch (ClusterSetExistException e) {
			// Cluster set exits, no problem.
			}
			Resource newResource = graph.newResource(l0.InstanceOf);
			graph.claim(newResource, l0.InstanceOf, null, l0.Entity);
			}
			});
			</pre>

	==Setting Literals==		==Setting Literals==

2011-01-28T15:54:29Z

← Older revision		Revision as of 15:54, 28 January 2011
Line 619:		Line 619:

	Completed code is in org.simantics.example.phases.AsyncPurchaseEditorFinal.java and completed ontology in example.pgraph.end		Completed code is in org.simantics.example.phases.AsyncPurchaseEditorFinal.java and completed ontology in example.pgraph.end

			[[Category: Database Development]]
			[[Category: Tutorials]]

2010-10-25T10:49:35Z

Example case: Product and Purchase management

← Older revision		Revision as of 10:49, 25 October 2010
Line 270:		Line 270:

	<pre>		<pre>
	Eclipse will complain that AsyncPurchaseEditorFinal.java does not compile, but it does not prevent starting the application.		Eclipse will complain that AsyncPurchaseEditorFinal.java does not compile, but it does not prevent
			starting the application.
	</pre>		</pre>

2010-10-25T10:49:16Z

Example case: Product and Purchase management

← Older revision		Revision as of 10:49, 25 October 2010
Line 268:		Line 268:

	Ontology that we are using is defined in ''Example.pgraph'' file. It is in ''org.simantics.example/graph'' folder. To run the example application, use ''simantics-example.product''. After starting the example product, you should get a user interface like the one in Figure 1.		Ontology that we are using is defined in ''Example.pgraph'' file. It is in ''org.simantics.example/graph'' folder. To run the example application, use ''simantics-example.product''. After starting the example product, you should get a user interface like the one in Figure 1.

			<pre>
			Eclipse will complain that AsyncPurchaseEditorFinal.java does not compile, but it does not prevent starting the application.
			</pre>

	[[Image:simantics_db_tutorial_start.png\|thumb\|600px\|center\|Figure 1: Tutorial application after one created product (Product 1) and one purchase.]]		[[Image:simantics_db_tutorial_start.png\|thumb\|600px\|center\|Figure 1: Tutorial application after one created product (Product 1) and one purchase.]]

2010-10-25T10:45:02Z

Example case: Product and Purchase management

← Older revision		Revision as of 10:45, 25 October 2010
Line 266:		Line 266:
	*https://www.simulationsite.net/svn/simantics/tutorials/trunk/org.simantics.example		*https://www.simulationsite.net/svn/simantics/tutorials/trunk/org.simantics.example
	*https://www.simulationsite.net/svn/simantics/tutorials/trunk/org.simantics.example.feature		*https://www.simulationsite.net/svn/simantics/tutorials/trunk/org.simantics.example.feature

	~~<pre style="white-space: pre-wrap">~~
	~~TODO : while the tutorial code exists, currently SVN contains version that is the result of this tutorial.~~
	~~</pre>~~

	Ontology that we are using is defined in ''Example.pgraph'' file. It is in ''org.simantics.example/graph'' folder. To run the example application, use ''simantics-example.product''. After starting the example product, you should get a user interface like the one in Figure 1.		Ontology that we are using is defined in ''Example.pgraph'' file. It is in ''org.simantics.example/graph'' folder. To run the example application, use ''simantics-example.product''. After starting the example product, you should get a user interface like the one in Figure 1.

2010-10-25T10:44:07Z

← Older revision		Revision as of 10:44, 25 October 2010
Line 1:		Line 1:
	~~TODO: walk through the tutorial, correct any errors found~~

	= Basic concepts =		= Basic concepts =
	;Session: Database session / connection that allows reading and writing the database using transactions.		;Session: Database session / connection that allows reading and writing the database using transactions.

2010-10-25T10:43:05Z

Supporting multiple items of the same product

← Older revision		Revision as of 10:43, 25 October 2010
Line 619:		Line 619:


	Completed code is in org.simantics.example.phases.AsyncPurchaseEditorFinal.~~hava~~		Completed code is in org.simantics.example.phases.AsyncPurchaseEditorFinal.java and completed ontology in example.pgraph.end

2010-10-25T10:41:52Z

Supporting multiple items of the same product

← Older revision		Revision as of 10:41, 25 October 2010
Line 617:		Line 617:

	[[File:simantics_db_tutorial_amount.png\|thumb\|center\|700px\|Figure 4: Amount column has been added into the table.]]		[[File:simantics_db_tutorial_amount.png\|thumb\|center\|700px\|Figure 4: Amount column has been added into the table.]]


			Completed code is in org.simantics.example.phases.AsyncPurchaseEditorFinal.hava