Problem: cascading deletes on subclass so they can be removed incl superclass object

Problem: If xref_label doesn't exist than the generator gives obscure error.
Solution: make a check in the language parser

Problem: getGeneratedKeys doesn't work in psql
Solution: put in a workaround???

Problem: xref requires lots of definition
Solution: default xref_field to autoid

Problem: everything should have id
Solution: add a big fat warning

Problem: Files don't seem to be stored in right folder
Solution: check if path is set correctly

Problem: SoapAPI has its own database instance
Solution: pass Servlet instance to api to get database

Problem: customizations of servlet are not supported, e.g. for custom soap api.
Solution: explain in manual how to set a custom class in hand-written that inherits generated one

Problem: subforms are not shown properly for MREFs
Solution: adapt generator to add mref to their filters.

Problem: plugins tend to depend on a data model module.
Solution: make data model into modules such that the class name is stable between apps.

Problem: type boolean is not supported
Solution: edit parser to map boolean to bool

Problem: type mref is not supported for querying!!!
Solution: hmmmm

= Some bugs that have been reported =


Problem: sometimes limited data needs to be loaded with the schema
Solution: enable a simple syntax to embed data in xml (or a link to csv?)

Issue: one wants to know how active a database instance is

Solution: enable logging on logon, number of queries fired per logon etc. Need a listener for that??? Or just a decorator???

Issue: one can have trouble to find the popup box (e.g. when adding stuff)
Solution: make that window modal and on top

Issue: sorting doesn't work anymore
Solution: make it an optional feature

Issue: what if we want to vary the columns dynamically
Solution: make a dynamic schema as plugin so they can be shown as if they were static
Alternative: generate tables on the fly.

Issue: what if we want to have an audit trail/"look back in time"?
Solution: have a versioned data model using additional fields. Can be done using a decorator (similar to security)

Issue: standard decorators should have a shorthand
Solution: make a type map.

Issue: very annoying that extends and implements cannot be mixed
Solution: translate extends to implements during parsing

Issue: people may want to add their own data type. E.g. pubmed link
Solution: mixture of decorator but we also need decorator on GUI level.

Issue: how about querying data between MOLGENIS instances
Solution: create a virtual user interface on top of existing models and use web services to query those.

Issue: for using ontologies, it would be great to be able to filter the data
Solution: enable filtering on xrefs

Issue: what if I want to make a portal website, so having some editable pages.
Solution: need a wiki style page system?

Issue: when extracting mysql the boolean default is '0'
Solution: cast defaults to their java class

Issue: what if I want to partially generate (so exend existing molgenis instance)
Solution: adapt language objects to set whether it should be included in generation.
Requires: that the model is also stored in generated result and that one can "import" this work.
Requires: that only changes are cascaded (!); so not only changed entities but also those depending (e.g. if xref/mref is affected).
Issue: what if I want to have my own generator?
Solution: extend language to include generators

multi column mrefs
##########
Fixes: search on xref/list values

Refactorings: clean up the DSL parsing, defaulting and validation steps.