| ||Ask HN: Can users update data in your app's DBs with SQL?|
5 points by james_anderson 3 days ago | hide | past | favorite | 3 comments |
|Do you find yourself in the difficult position of having users who make updates to the database owned by your application?|
In my experience this happens because the application has gaps in functionality or the process would be much faster to complete in SQL then it would in the app. This makes turning off access difficult as these processes are often business critical.
- Short-term - people make mistakes and corrupt/destroy data or cause downtime.
- Long-term - data can't be trusted.
I'd be interested to hear people's war stories and the methods/tech used to escape.
My thoughts are:
1. Track scripting
2. Catalogue reasons for scripting
3. Address the functionality gap that will remove the most common reason for scripting
4. Remove access to tables users were updating via SQL before functionality gaps were filled
5. Continue 1-4 until done
| Apply to YC