创建自定义ODBC驱动程序 [英] Creating a custom ODBC driver

问题描述

在我目前的工作中，我们希望实现我们自己的odbc驱动程序，以允许许多不同的应用程序能够作为数据源连接到我们自己的应用程序。现在，我们正试图权衡开发我们自己的驱动程序的选项，以实现规范，这是巨大的或使用一个SDK，允许程序员填充数据特定的部分，并允许更高

At my current job, we're looking to implement our own odbc driver to allow many different applications to be able to connect to our own app as a datasource. Right now we are trying to weigh the options of developing our own driver to the implementation spec, which is massive, or using an SDK that allows for programmers to 'fill in' the data specific parts and allow higher levels of abstraction.

有没有人实现了自定义odbc驱动程序？你遇到了什么陷阱？你自己做了什么好处？你估计需要多少工时？您是否使用SDK，如果是，您从该方法中看到了什么好处/缺点？

Has anyone else implemented a custom odbc driver? What pitfalls did you run into? What benefits did you see from doing it yourself? How many manhours would you approximate it took? Did you use an SDK, and if so, what benefits/downsides did you see from that approach?

任何意见和答案将非常感谢。非常感谢！

Any comments and answers would be greatly appreciated. Thanks!

编辑：我们正在尝试使用C编写的代码保持可移植性。

We are trying to maintain portability with our code, which is written in C.

推荐答案

我没有，但我曾经在一家公司做过这样的采访。他们做了
一个叫做AMPS的4GL / DBMS产品，它和MUMPS是一样的架构 - 一个具有集成4GL的分层数据库（这种系统的整个类型在20世纪70年代出现）。他们有相当大的遗留代码库和客户希望使用MS Access连接到它。

I have not, but I once interviewed at a company that had done exactly this. They made a 4GL/DBMS product called AMPS of the same sort of architecture as MUMPS - a hierarchical database with integrated 4GL (a whole genre of such systems came out during the 1970s). They had quite a substantial legacy code base and customers wishing to connect to it using MS Access.

采访我的主要开发者分享了一些关于这个的故事。显然，这是非常痛苦的做，不应该轻率。

The lead developer who interviewed me shared some war stories about this. Apparently it is exceedingly painful to do and shouldn't be taken lightly. However, they did actually succeed in implemnenting it.

这样做的一个替代方法是提供一个数据集市/ BI产品（按照SAP BW的思路）您的应用程序数据在一个外部数据库，并将其按摩为更友好的格式，如星形或雪花模式。

One alternative to doing this would be to provide a data mart/BI product (along the lines of SAP BW) that presents your application data in an external database and massages it into a more friendly format such as a star or snowflake schema.

这将遭受不支持实时访问，可能比ODBC驱动程序更容易实现（更重要的是维护）。如果您的实时访问要求是合理可预见和有限的，您可能会公开一个Web服务API来支持这些。

This would suffer from not supporting real-time access, but might be considerably easier to implement (and more importantly maintain) than an ODBC driver. If your real-time access requirements are reasonably predicitable and limited, you could possibly expose a web service API to support those.

这篇关于创建自定义ODBC驱动程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！