Timeline for Using ORMs in two separate programs which share a DB
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2015 at 10:42 | comment | added | gbjbaanb | write all your queries using stored procedures - ten you can change your DB schema and keep a fixed API. | |
| Oct 13, 2015 at 10:40 | answer | added | Idan Arye | timeline score: 0 | |
| Oct 13, 2015 at 8:48 | comment | added | TylerAndFriends | @JeroenVannevel Usually I would change the DB schema via an ORM, but yes you're correct. | |
| Oct 13, 2015 at 7:19 | comment | added | Jeroen Vannevel | If you change the DB schema you'll always have to change the clients, ORM or not. | |
| Oct 13, 2015 at 5:30 | answer | added | Cody Banks | timeline score: 2 | |
| Oct 13, 2015 at 4:28 | comment | added | Sjoerd Job Postmus | Just a quick question: can't you write two generators which generate the ORM model files from a shared description? That way you still have 1 representative definition of your model. For bonus points, let it also generate the SQL schema definition (or, if both your libraries support it, let both of them generate the definition, and assert that they generate the same definition) | |
| Oct 13, 2015 at 4:19 | review | First posts | |||
| Oct 13, 2015 at 7:24 | |||||
| Oct 13, 2015 at 4:14 | history | asked | TylerAndFriends | CC BY-SA 3.0 |