|
> PostgreSQL has been declared taboo by the corporate security team, for some reason I cannot fathom.
Well a reasoning would be helpful. I'm not sure I can build up a case because your company doesn't like PostgreSQL for some unknown reason  . I hope you can understand that isn't a good argument .
Most of the reasons for choosing PG only are technical in-fact, and its about reducing the amount of development. We don't use an ORM by choice, because our requirements need to push the database heavily so we work with transformation layers (HoneySQL) but not ORM's, basically we're pretty much translating our query language to SQL on our own.
So for translating some of our uses into other platforms, this isn't trivial. We'd need to write the abstractions for this, and whats more - make sure the platforms are constantly tested like anything. This is why we'd welcome help from the community if it was required, but as yet we've only had a couple of people offer to help, but alas no patches.
And, we're not sure that translating it brings technical benefits either - although I would argue Oracle as a platform might help - especially considering some of its performance related tooling. We use a lot of JSON features, and planning on doing more of that - and each of these platforms has their own ways of dealing with JSON, which would make it tricky. When one diverges at this level, we find ourselves cutting support in PDB for certain backends, which we ended up doing all the time for HSQLDB (which is why we removed it), which is okay for the consumer but the code and our API decisions can be very murky in this world - ie. we have to design around the ability that certain backends won't have XyZ feature.
So if anything, the reason for transferring to other platforms isn't very technical by most peoples standards, except for perhaps the familiarity argument. So in that case, the reasoning I think needs to become a non-technical one - a space we as engineers don't really make calls on most of the time. I personally can't be convinced to work on a MySQL port (and continue to maintain it also, alongside PG) without good reason, when we have so many other problems that need solving above and beyond that, for example - problems that stop our currently happy PostgreSQL users go further and do more things.
Having said all that, we do welcome patches . If someone sent us a MySQL patch, we'd happily review and consider it, TBH.
|
