| > - A much better experience in Java and .NET drivers, including SQL custom data types. So I'll admit, I haven't used the Oracle Provider for .NET since 2017. Oracle.DataAccess is not the friendliest library to work with and I've seen some weird issues with pooling in past use. Devart has a good provider, but somewhat limited in free features (still a better general experience than Oracle's provider, but you don't get all the custom bits unless you pay). PostgreSQL on the other hand has a very nice ADO Provider in NpgSql. It can look a bit daunting with all the config options offered but overall I'd still say it's a better API experience than Oracle.DataAccess. > - A much better developer experience for stored procedures, with proper packaging, compilation to native code, graphical debugger. Oh I do miss Oracle Packages so so much. Yeah, they could be a bit annoying to deal with from a 'gobs of code in one file' standpoint, but it's -so- nice to just have PKG_CUSTOMER, PKG_LOCATION instead of having to scroll through all the individual stored procedures, having to guess whether people named things in a way you could find them... Edit: For a long time, you could have added
- Arguments about how to store a boolean value But thankfully Oracle finally took care of that in 12. |