Timeline for auto generated web CMS for pre-existing SQL db?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 28, 2016 at 15:51 | answer | added | TurbuLenz | timeline score: 1 | |
Mar 10, 2016 at 13:07 | audit | Suggested edits | |||
Mar 10, 2016 at 13:08 | |||||
Feb 28, 2016 at 17:27 | comment | added | MikaelW | The real app itself, for the general public, is 100% custom and is developed as such. What i'm talking about here is the cms part. A way for app managers to change the app data in a safe way. That cms is 90% generic and 10% custom hence my question to auto generate the 90%. | |
Feb 28, 2016 at 15:36 | comment | added | Lightness Races in Orbit | So, in other words, your app needs to do things that follow from a requirements document, and cannot simply be auto-generated from a database schema. Well then isn't that your answer? | |
Feb 28, 2016 at 14:30 | comment | added | MikaelW | :-) No. In phpmyadmin, there wouldn't be the foreign key link using a nice name instead of id (see screenshot #3). Also, the DB is not necessarily MySQL Also, the solution should allow custom validation and hide the complexity of the low level DB. To be used by someone who manage the app but is not a techie. Thanks | |
Feb 28, 2016 at 14:24 | comment | added | Lightness Races in Orbit | Sounds like what phpMyAdmin does :) | |
Feb 28, 2016 at 14:09 | history | edited | MikaelW | CC BY-SA 3.0 |
added 2 characters in body
|
Feb 28, 2016 at 14:07 | history | edited | gnat | CC BY-SA 3.0 |
edited body
|
Feb 28, 2016 at 14:04 | history | asked | MikaelW | CC BY-SA 3.0 |