创建自定义 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 的分层数据库(此类系统的整个类型在 1970 年代出现).他们有相当多的遗留代码库，客户希望使用 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屋！