The automatically generated insert triggers on the latest views have been simplified such that attribute metadata values default to the anchor metadata value if not specified. This makes insertion into the view (in order to create a new instance of the anchor and all attributes) as simple as the following code shows:
insert into lAC_Actor (
values (42, 'Lars S', '1972-08-20', 'Male', 'Master', '2009-09-21');
If there is a need to ‘update’ the name this can also be done using the insert trigger on the latest view (given that the surrogate key generated for AC_ID in the previous step was 1):
insert into lAC_Actor (
values (1, 'Lars R', '2004-06-19', 43);
We are proud to announce that our Minified Layout Engine reached 7th place in the JS1k competition, out of 427 submitted demos. We will be eagerly awaiting some of the nice prices coming our way. The full engine is used in our online modeling tool Anchor Modeler, and has many more features.
We have added a number of video tutorials introducing the basic concepts of Anchor Modeling by using the online modeling tool. The tutorials can be found by clicking here. We will also continue to add tutorials on that page.
You can now follow us on twitter! Our profile is available here: http://twitter.com/anchormodeling
The online modeling tool can now produce an SVG (Scalable Vector Graphics) of the model. This enables further (and lossless) adjustments of the layout and design if the SVG is edited in a program such as the open source editor Inkscape. We have, for example, done this for the figures in our paper submitted to the Data & Knowledge Engineering journal. An example showing the evolution of an anchor schema can be seen below, which was edited to shade the original model.
We have formalized the translation of an anchor schema to an XML document. This formalization is referenced by our academic papers. Read it here:
From Anchor Model to XML
We have formalized the translation of an anchor schema to a relational database schema. This formalization is referenced by our academic papers. Read it here:
From Anchor Model to Relational Database
We have formalized the by us suggested naming convention to use in Anchor Modeling. This is also the convention used in the online modeling tool and is referenced by our papers. Read more about it here:
Anchor Modeling: Naming Convention
For our paper submitted to DKE (Data & Knowledge Engineering) we have enhanced earlier made performance tests. These now test and compare performance in an anchor database to that in a less normalized database, with respect to several different conditions. The automated scripts for doing the tests are available here:
Performance Testing in Anchor Databases
Our contribution can be found by clicking here. It’s an extremely minified (1016 bytes) version of the layout engine used in the online modeling tool. You can still build a node/edge model in it though.