Changes between Initial Version and Version 1 of MolenisBug


Ignore:
Timestamp:
2009-08-29T21:35:58+02:00 (15 years ago)
Author:
Morris Swertz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MolenisBug

    v1 v1  
     1Problem: cascading deletes on subclass so they can be removed incl superclass object
     2
     3Problem: If xref_label doesn't exist than the generator gives obscure error.
     4Solution: make a check in the language parser
     5
     6Problem: getGeneratedKeys doesn't work in psql
     7Solution: put in a workaround???
     8
     9Problem: xref requires lots of definition
     10Solution: default xref_field to autoid
     11
     12Problem: everything should have id
     13Solution: add a big fat warning
     14
     15Problem: Files don't seem to be stored in right folder
     16Solution: check if path is set correctly
     17
     18Problem: SoapAPI has its own database instance
     19Solution: pass Servlet instance to api to get database
     20
     21Problem: customizations of servlet are not supported, e.g. for custom soap api.
     22Solution: explain in manual how to set a custom class in hand-written that inherits generated one
     23
     24Problem: subforms are not shown properly for MREFs
     25Solution: adapt generator to add mref to their filters.
     26
     27Problem: plugins tend to depend on a data model module.
     28Solution: make data model into modules such that the class name is stable between apps.
     29
     30Problem: type boolean is not supported
     31Solution: edit parser to map boolean to bool
     32
     33Problem: type mref is not supported for querying!!!
     34Solution: hmmmm
     35
     36= Some bugs that have been reported =
     37
     38
     39Problem: sometimes limited data needs to be loaded with the schema
     40Solution: enable a simple syntax to embed data in xml (or a link to csv?)
     41
     42Issue: one wants to know how active a database instance is
     43
     44Solution: enable logging on logon, number of queries fired per logon etc. Need a listener for that??? Or just a decorator???
     45
     46Issue: one can have trouble to find the popup box (e.g. when adding stuff)
     47Solution: make that window modal and on top
     48
     49Issue: sorting doesn't work anymore
     50Solution: make it an optional feature
     51
     52Issue: what if we want to vary the columns dynamically
     53Solution: make a dynamic schema as plugin so they can be shown as if they were static
     54Alternative: generate tables on the fly.
     55
     56Issue: what if we want to have an audit trail/"look back in time"?
     57Solution: have a versioned data model using additional fields. Can be done using a decorator (similar to security)
     58
     59Issue: standard decorators should have a shorthand
     60Solution: make a type map.
     61
     62Issue: very annoying that extends and implements cannot be mixed
     63Solution: translate extends to implements during parsing
     64
     65Issue: people may want to add their own data type. E.g. pubmed link
     66Solution: mixture of decorator but we also need decorator on GUI level.
     67
     68Issue: how about querying data between MOLGENIS instances
     69Solution: create a virtual user interface on top of existing models and use web services to query those.
     70
     71Issue: for using ontologies, it would be great to be able to filter the data
     72Solution: enable filtering on xrefs
     73
     74Issue: what if I want to make a portal website, so having some editable pages.
     75Solution: need a wiki style page system?
     76
     77Issue: when extracting mysql the boolean default is '0'
     78Solution: cast defaults to their java class
     79
     80Issue: what if I want to partially generate (so exend existing molgenis instance)
     81Solution: adapt language objects to set whether it should be included in generation.
     82Requires: that the model is also stored in generated result and that one can "import" this work.
     83Requires: that only changes are cascaded (!); so not only changed entities but also those depending (e.g. if xref/mref is affected).
     84Issue: what if I want to have my own generator?
     85Solution: extend language to include generators
     86
     87multi column mrefs
     88##########
     89Fixes: search on xref/list values
     90
     91Refactorings: clean up the DSL parsing, defaulting and validation steps.