Print Page | Close Window

Connecting to an Ingres database

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce Classic
Forum Discription: For .NET 2.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1023
Printed Date: 10-Jun-2026 at 7:09pm


Topic: Connecting to an Ingres database
Posted By: esky_mo
Subject: Connecting to an Ingres database
Date Posted: 14-Dec-2008 at 5:37pm
I'm having trouble connecting to an Ingres database on my local machine through the Ideablade object mapper. Ideablade passes the Test connection, but when it comes time to add the classes in, I get an unable to connect error.

I can connect and query in my .Net code using the System.Data.Odbc objects with a plain connection string (pasted below), and with a prebuilt ODBC connection.

Provider=MSDASQL.1;DRIVER=Ingres;SRVR=(local);DB=demodb;Persist Security Info=True;SELECTLOOPS=N;

So far the only data provider in the list I've had any luck with is "Microsoft OLEDB Provider for ODBC Drivers", am I wrong to assume there should be an Ingres driver here that I could be missing?

Many thanks,
Keith


Replies:
Posted By: davidklitzke
Date Posted: 15-Dec-2008 at 8:47am
Ingres is not one of our officially supported databases. 
 
That is not to say that you will not be able to get IdeaBlade to work with Ingres.
 
However for Ingres support, you will need a fully compliant OLEDB provider.  This may explain why you have had some minor success with Microsoft OLEDB Provider for ODBC Drivers.  Personally, I have never had complete success with this provider.

Posted By: esky_mo
Date Posted: 15-Dec-2008 at 3:06pm
Thanks for your reply David, I do remember reading somewhere in my research that IdeaBlade can support ingres, but I now realise that I was reading about the EF version (linked). %20 - http://www.ideablade.com/DevForceEF/ProductDocumentation/DevForceEFInstallationGuide.html

Would it be easier for me to hook into ingres using EF or am I at the same stumbling block?

Posted By: davidklitzke
Date Posted: 15-Dec-2008 at 4:33pm
It is a different issue with EF.  For Classic, the issue is getting the DevForce Framework to talk to the database.  For EF the issue is getting the Entity Framework to talk to the database.  Initially, the Entity Framework only talked to SQL Server. We have only recently heard of the Entity Framework talking to Oracle, so it may be some time before we see Ingres support in EF.
 

Posted By: esky_mo
Date Posted: 15-Dec-2008 at 4:49pm
Thanks muchly, you've been most helpful. I'll have to keep an eye on the Entity framework as I do quite a bit of integration work which often includes some very interesting databases that need to be compared to sql server data

Cheers,
Keith


Print Page | Close Window