No worries, I've also just found out that there's an alternative syntax which will go at the end of the SELECT statement, so I can use one of RANGE_POST_SELECT or RANGE_POST_LOCK.
Alan -----Original Message----- From: Michael Dick [mailto:[email protected]] Sent: 28 June 2009 22:26 To: [email protected] Subject: Re: DBDictionary appendSelectRange No objection from me (sorry for the late response, trying to catch up on email over the weekend). -mike On Sat, Jun 27, 2009 at 3:49 AM, Miłosz Tylenda <[email protected]> wrote: > Alan, > > It is my understanding that the main difficulty you have with range in > Ingres is that that database requires "FIRST n" and "OFFSET m" in different > parts of SELECT statement and OpenJPA supports only the cases where such > clauses are located next to each other. > > I am OK with making toOperation method protected. Will change it in trunk > and 1.3.x if other committers have no objections. > > Regards, > Milosz > > > Hi all > > > > > > > > I've just found out that Ingres now supports an "offset" for SELECT > > statements; SELECT FIRST n FROM table OFFSET m; > > > > > > > > Looking at the appendSelectRange method, it doesn't look like I can put > > the "offset" keyword after the FROM clause, so I will need to override > > the toOperation method - except that the toOperation method which does > > the work is private, so I would need to override every toOperation > > method in order for it to be called. > > > > > > > > Any ideas why this method is private? Could it be relaxed to protected? > > > > > > > > Alan > > > > > > > > >
