Hi, I've used to look after the Ingres implementation but had to drop it because I didn't have time any more to look after it.
I think I'll have an hour or two this week to have a go at fixing this. Jim, are you able to send me a test case I can debug against (maybe a copy.in script and the Linq query(s))? Cheers, Thomas On Oct 9, 3:14 pm, Shuggie <[email protected]> wrote: > On Oct 8, 6:45 am, Jim <[email protected]> wrote: > > > > > > > Hello All, > > > Select Issue > > > var q = from planTable in cispDB.Plan > > where (planTable.PlanNo == "ABC1234" || > > planTable.PlanNo == "ABC1235") > > join planLaTable in cispDB.PlanLa on > > planTable.PlanNo equals planLaTable.PlanNo > > join localAuthTable in cispDB.LocalAUtH on > > planLaTable.LaCode equals localAuthTable.LaCode > > select new { planTable.PlanNo , > > planLaTable.LaCode, localAuthTable.LaName, planTable.TownCode }; > > > Investigation showed that the eventual SQL query did not bracket the > > OR at all. To get it to work temporarily I changed SqlBuilder.cs in > > the BuildWhere method and added > > if (!IsHavingClause(whereExpression)) > > { > > string be = BuildExpression(whereExpression, > > queryContext); > > if (be.Contains("OR")) > > be = "(" + be + ")"; > > whereClauses.Add(be); > > //whereClauses.Add(BuildExpression > > (whereExpression, queryContext)); > > } > > > Update Issue > > > I cannot get it to update a field ! Code I am using is beow, if > > anybody has got an update to work with Ingres (I'm using Ingres 2.6 at > > the moment) I would be most appreciated of some help. > > > CISpProd cispDB = new CISpProd(new IngresConnection > > (connString)); > > > Plan pl = (from c in cispDB.Plan > > where c.PlanNo == "ABC1234" > > select c).First<Plan>(); > > > pl.TownCode = "Jim"; > > > cispDB.SubmitChanges(); > > > Hoping somebody can assist > > > Thanks, > > Jim > > Hi Jim, > > I don't know anything about DbLinq but I do know Ingres. > > It looks like DbLinq is using the .Net data provider for connection > and you say you're using Ingres 2.6. The Ingres .Net Data Provider > wasn't released under 2.6 and doesn't support it directly. It's > technically possible to use it to connect to a 2.6 JDBC server rather > than the DAS server but it's not supported and I know of a few > problems with it. There is a supported way to connect to 2.6 via .Net > and that is via an Ingres 2006 installation and an Ingres net vnode. > That is you point yor .Net connection to a DAS server in a 2006 > installation where you have a vnode defined that points to your 2.6 > isntallation and specify the database name as "vnode::dbname". > > Also I notice that the source for DbLinq includes the > Ingres.Client.dll i.e. the .Net data provider. However it looked like > the Ingres part of the DbLinq source hadn't been downloaded for some > time - so it may be worth downloading the latest dll from > esd.ingres.com. > > HTH > Paul- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
