Timeline for Does it make sense to place constraints in the code instead of in the database?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2017 at 16:00 | comment | added | Paul | @kilianFoth Not to be pedantic, but technically SQL databases were invented after non-relational databases. They have come back into vogue order to solve scalability (and other) problems that SQL databases have a harder time with. | |
| Sep 29, 2017 at 15:14 | comment | added | JeffO | @Neil - I agree, but if you're going with a relational database with any kind of power, let it do what it does best. Otherwise, you have to deal with the disadvantages and get little upside. | |
| Sep 29, 2017 at 13:57 | comment | added | Kilian Foth | Sure, non-relational DBs have their place. But they weren't invented because the relational model was too limiting. They were used first for extremely (Yahoo, Facebook...) big data sets when relational DBs could not scale enough at all. | |
| Sep 29, 2017 at 13:54 | comment | added | Neil | To be fair, there has been a movement towards No-SQL type databases which are generally more flexible than their traditional database counterparts. There are certainly disadvantages to this approach, but it does make the program the controller of its data. That said, I do think it is wrong to attempt to make a traditional database act like a NO-SQL database. | |
| Sep 29, 2017 at 10:54 | history | answered | Kilian Foth | CC BY-SA 3.0 |