Timeline for Why can't I just let customers connect directly to my database?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2020 at 4:20 | history | edited | poolie | CC BY-SA 4.0 |
added 492 characters in body
|
| Apr 21, 2020 at 4:17 | comment | added | poolie | @Dragonel I know how to write SQL but I pay (lots!) of companies either for access to well-curated data, or for goods and services to which the data is ancillary. | |
| Apr 21, 2020 at 0:23 | history | edited | poolie | CC BY-SA 4.0 |
edited body
|
| Apr 20, 2020 at 16:20 | comment | added | Dragonel | "The customer wants to do complex operations on the data that are easily expressed in SQL, and they know how to write SQL." This is point one to my mind - Unless your users are advanced SQL users this won't work - and if they are, what are they paying you for anyway? | |
| Apr 19, 2020 at 22:07 | comment | added | Thomas W | Good answer. It describes a number of conditions, all of which must be satisfied, and if all are satisfied it might conceivably be OK to give external actors relatively direct access to the database (though better options such as GraphQL may exist). In all other situations it's not a great idea. | |
| Apr 17, 2020 at 22:11 | history | answered | poolie | CC BY-SA 4.0 |