Torsten Curdt dijo: > <snip/> > >> I dont agree. The LIMIT 5+1 is just a internal issue. From the user >> view. he never knows we was asking 5+1 rows. He never can access the >> 5+1 row. even if it exists. > > That is exactly what I was trying to say ;) > > Keep in mind we have user -> esql -> classes -> resultset > > Who should fix the +1 issue? esql or the class? And if the class (which > can be confusing) - how... > > ...that's what I gonna put under my pillow tonight ;)
Lets put a good description of the hack into the code. Why we did that? The best solution can be if there are another JBDC function that support that. But I dont know if this function exist. Then I discarded this option. :-( I think that the helper class must resolve this issue. But it must know when to hack and when not. Maybe adding a parameter to the function that tell if we want to know if there are more results or not. This is again hidden from the user view. The user does not work directly with the esql helper class or with the internally processing of the esql.xsl. For me the solution must be clear for the developers of any of the files the helper class and/or the esql.xsl I think we have the 1st milestone here. An agree that this will improve the database experience. Now we must agree with the solution. Please wait until the solution is done before tell if this is ugly ;-). Best Regards, Antonio Gallardo. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
