This document details the steps required to provide Microsoft Entity Framework access to ODBC to JDBC Bridge Schema Objects using the
The following prerequisites must be in place for this solution to be possible.
An ODBC to JDBC Bridge DBMS hosting the required Schema Objects needs to be available. In this document we shall make an ODBC to JDBC bridge connection to another Virtuoso Northwind Demo database to demonstrate the process.
An ODBC to JDBC Bridge Driver is required for Linking the ODBC to JDBC Bridge Schema Objects into the Virtuoso Server.
jdbcma will be assumed to exist on the machine hosting the Virtuoso Server.
A Virtuoso installation including the Virtuoso Universal Server and ADO.NET Entity Framework Provider is required. The Virtuoso components used must be Release 5.10.x or above, this being the minimum version containing support for Microsoft Entity Frameworks.
Microsoft Visual Studio 2008 Service Pack 1 is required, this being the only version containing the necessary Entity Framework support available at the time of writing.
The Visual Studio 2008 Entity Data Model (EDM) requires that all primary keys are *NOT* Nullable. Visual Studio will fail to generate an EDM, if any are. Therefore, ensure any primary keys to be used are defined as not nullable in the ODBC to JDBC Bridge database schema, before attempting to generate an EDM. In the case of the ODBC to JDBC Bridge Virtuoso Northwind Demo database, all primary keys are not nullable. Thus, this should not be an issue in this case.
The Virtuoso Virtual Database engine uses ODBC as the connectivity mechanism for linking remote database objects into its local schema.
Thus, an ODBC to JDBC Bridge Driver must be available with a suitably configured DSN for connecting to the target database.
Installation instructions for the
Now that a Microsoft Entity Data Model has been created for the ODBC to JDBC Bridge Virtuoso Northwind Demo database, Entity Framework applications can be created to make use of it.