Hi Jon, my gut feeling tends want to believe what you are saying. I need to have a look at the issue itself first, but let's expand on this later on.
Werner Jon Wilmoth wrote: > Hi Ralf, I've commented on the ticket, but the gist of it is that I > was able to use the existing style of SQL (no nested sub selects) and > retrieve the corrrect number of records from the database with simple > JDBC api calls. This leads me to believe that the generated SQL > doesn't necessarily need to change to fix this bug...just the result > set processing logic. Thanks, Jon > > > ----- Original Message ---- From: Ralf Joachim > <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent: Monday, > May 26, 2008 11:53:04 AM Subject: Re: [castor-user] [JDO] CASTOR-1252 > Limit clause on model with collection > > Hi Jon, > > have you seen my comment on CASTOR-1252? > > What did you had in mind when you offered to help to resólve this > issue? > > Regards Ralf > > > Ralf Joachim schrieb: >> Hi Werner, >> >> while some database engines have problem with LIMIT clauses, the >> issue in question is about a internal problem of Castor. As already >> said I'll explain what happens in a minute at the issue itself. >> >> Regards Ralf >> >> >> Werner Guttmann schrieb: >>> Same here. Thanks for your offer, Jon. Being short of time a bit >>> these days, let me just get some of the knowledge across I do >>> remember from the days back then. >>> >>> a) Some RDBMS engines do not have support for a LIMIT clause (or >>> anything similar). b) Some (other) RDBMS do have limited support >>> only for LIMIT clauses (or similar constructs) only. c) Some >>> RDBMS do have full support for LIMIT clauses, though restrict >>> this on single table entities only. >>> >>> In other words, it might as well be that a solution will have to >>> happen at Castor's code level, as the current (limited) solution >>> makes use of DB-specific constructs only. >>> >>> Werner >>> >>> Ralf Joachim wrote: >>>> Hi Jon, >>>> >>>> we appreciate your offer to help resolving this realy critical >>>> issue. To start with things I will try to outline my >>>> understanding of what happens later on today at the issue. >>>> >>>> Having said that I have already started to work at a series of >>>> refactorings of SQL engine to improve SQL generation. In >>>> addition a GSoC student will work at improvement of OQL engine >>>> this summer. >>>> >>>> Regards Ralf >>>> >>>> Jon Wilmoth schrieb: >>>>> Are there any suggested workarounds for >>>>> http://jira.codehaus.org/browse/CASTOR-1252 (Limit clause on >>>>> model with collection...causing inaccurate search results)? >>>>> Better yet any progress on a resolution? Given the frequency >>>>> of 1:M relationships in software and the fact that "child" >>>>> records are typically in need of "paging" I completely >>>>> understand the bug's critical priority and would like to help >>>>> get this 2+ year old bug knocked off. >>>>> >>>>> >>>>> >>>>> Thanks, Jon >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
