Re:Database drivers: Naughty or nice?
by tabtab on Monday December 12, 2022 @06:42PM
(#33962122)
It generally takes roughly 5 years for such standards to trickle into common systems. But separate software could make a server gateway/portal to those database products without it. In other words, a server-based adaptor. Database-vendor-specific services could be fairly easily built in say PHP or Python. They'd still conform to the standard (using XML and/or JSON), but only implement a gateway for specific database brands. It's a start...
[ Parent
| on HN ]
Adding a layer slows things down and uses more memory, even if just a tiny bit, but for large result sets, I fear it will be a lot.
In addition it likely initially a) will be buggy and b) won’t support every feature of every vendor.
I think that’s a hard to win battle.
Re:Database drivers: Naughty or nice?
by tacostakohashi on Monday December 12, 2022 @06:59PM
(#33962335)
Sure, that could be done... but it would be dramatically slower that any of the existing drivers. As much as the vendor drivers / odbc / jdbc have their annoying quirks, the wire protocols are pretty efficient.
It could have a binary format option (in addition to those formats listed). But also many kinds of apps don't need heavily compressed/compact data transfers. The "old" way won't go away, just have an alternative.
Re:Database drivers: Naughty or nice?
by tacostakohashi on Monday December 12, 2022 @08:08PM
(#33963187)
Ok, but they already have a binary format...
What is the advantage of your hypothetical binary format (which doesn't exist), (in addition to those formats listed), over the binary formats which have existed for decades?