3 ms·
You missed one critical situation: "You must use X because this required / desired product uses X as a backend". Thus, I pay Oracle every year because some Sof
by protomyth 10y ago
You missed one critical situation: "You must use X because this required / desired product uses X as a backend". Thus, I pay Oracle every year because some Software Developer used it in a product.
- AndyNemmity 10y agoCertainly true with a variety of products. You are stuck with certain vendors because that's what was used, etc etc.
- brazzledazzle 10y agoOne thing you gotta give Atlassian credit for is supporting multiple SQL databases. They put in the time and effort and that can be a rare thing in enterprise or b2b software.
- tracker1 10y agoIt somewhat depends on how much code targets DB specific features... if your data store is relatively "dumb", it's easy enough to abstract out ANSI queries with specific abstractions to keep the code very generic. I'd say that mysql is probably the oddest one out in a lot of cases. The db/table creation is probably the one part that requires the most tweaking. I have to admit, I always hated MS Enterprise Library, specifically the Data Application Blocks (I think that's what it was called). Mostly because it was a lot of abstraction for zero gain when you only targeted one database. The only time it was worthwhile was when I worked on an application targetting multiple backend databases. Even then it was a lot of work.