4 ms·
Were you using an ORM? I ask because most people use database switching as a selling point for using an ORM. I'm rather indifferent on the matter, but I'm curi
by throwaway55554 7y ago
Were you using an ORM? I ask because most people use database switching as a selling point for using an ORM. I'm rather indifferent on the matter, but I'm curious.
- kirstenbirgit 7y agoYou still have to migrate the data. I faced the same kind of dilemma, but with MySQL, and kind of noped out when I got to stuff like [0]. [0] https://stackoverflow.com/a/87531/1210797 https://stackoverflow.com/a/87531/1210797
- jtdev 7y agoHa! This selling point is just one in a miserable litany of poor reasons to use an ORM - you absolutely cannot simply switch between databases without doing some work to ensure that the data is migrated correctly and the SQL statements translate properly.
- nomel 7y agoYeah, but verification of correctness is much less work than implementation.
- jimbokun 7y agoAs an alternative to an ORM, there is another great abstraction layer that works across a large number of databases. It's called SQL!
- kingbirdy 7y agoThat's true in theory, but unfortunately you can still run in to issues when different databases support different parts of SQL, and the db you're migrating from has different features than the one you're migrating to.
- shakna 7y agoThere are a huge number of differences in the SQL supported by different engines. You can't just switch from one to another, unless you're only using a small subset of SQL to begin with.
- imtringued 7y agoUntil you realize that not even booleans are standardized between SQL dialects...
- legulere 7y agoHow do you insert a row and get the automatically set Id set by the database portably? That’s a standard create operation.
- imtringued 7y agoAn ORM does indeed force you to write lowest common denominator code but I wouldn't rely on that.