| | | |
| Should be easy .. update the files, run the migrat | | Should be easy .. update the files, run the migrat |
| ion files (for database schema updates) and everyt | | ion files (for database schema updates) and everyt |
| hing should work already ... (migration files aren | | hing should work already ... (migration files aren |
| 't really powerful .. but with a bit of luck .. th | | 't really powerful .. but with a bit of luck .. th |
| ey might even work sometimes) | | ey might even work sometimes) |
| | | |
| ** How extend able is the result ? (e.g. Imagine i | | ** How extend able is the result ? (e.g. Imagine i |
| would like to add a workflow where changes get on | | would like to add a workflow where changes get on |
| line once an administrator approves them) ** | | line once an administrator approves them) ** |
| | | |
| t |
| t | Well.. i doubt the extensibility a bit.. but if yo |
| | | u remove all the autogenerated code and do it by h |
| | | and.. there shouldn't be any problem left ..
|
| | | |
| | | |
| ** How much duplication was necessary ? (e.g. need | | ** How much duplication was necessary ? (e.g. need |
| to describe the models in the database as well as | | to describe the models in the database as well as |
| in code or xml ? / need to describe attributes of | | in code or xml ? / need to describe attributes of |
| models in models and views ?, etc.) ** | | models in models and views ?, etc.) ** |
| | | |
| well.. for "normal" types it's not all that bad.. | | well.. for "normal" types it's not all that bad.. |
| e.g. if you add a new string .. simply add the mig | | e.g. if you add a new string .. simply add the mig |
| ration file .. and modify the _form.html (no idea | | ration file .. and modify the _form.html (no idea |
| if this is supposed to happen automatically ?) .. | | if this is supposed to happen automatically ?) .. |
| and this should be .. it.. | | and this should be .. it.. |
