On Tue, 12 May 2009, Derrell Lipman wrote: > On Tue, May 12, 2009 at 4:59 PM, Michael Helwig <[email protected]>wrote: > >> Hi, >> I'm still working with qooxdoo's remote tables and I'm having problems >> with getting the right data from mysql. The trouble is that qooxdoo at >> the beginning wants to have rows 0 to 100 and, if the table is >> scrolled to the appropriate position, qooxdoo requests the next 50 >> rows, etc. >> It is rather easy to get the right results from mysql if the table is >> sorted by strictly successive id's, i.e. if there is no number left >> out. After thinking things through I also managed to get the remote >> table working correctly with tables in which some id's are missing, >> i.e. where numbers are not strictly successive. I also managed to deal >> with ascending and descending ordering by id. >> What I'm still not able to do is to sort tables correctly (ascending >> or descending) by other column titles which contain text and / or >> which are not unique. My question is whether there is some easy way to >> do this. Has somebody done it (I guess so) and can point me to the >> right direction? I guess I have to solve that somehow in mysql but I >> want to make sure that there is no easy way in qooxdoo that I'm >> ignorant of. >> > > Hi Michael. The easy way is to disable sorting on all columns. That > completely eliminates the problem. :-) > > Yes, you're right, since you're using a remote model and not all of the data > is available at the client, the sorting has to happen at the backend. You > may consider whether it makes sense to sort by every column, and disable > sorting on those with which it makes no sense... or which it would be > extremely difficult or time consuming to sort by at the backend. > > You're likely making good use of the OFFSET/LIMIT clauses of SQL by now (I'm > assuming that mysql implements those), in order to obtain the correct range > of rows. You can use those regardless of your ORDER BY clause, so that would > work regardless of which column is selected at the client for sorting.
Note, though, that OFFSET/LIMIT might give rather unpredictable results IF NOT used together with ORDER BY. Especially after inserting or deleting rows the order in which the DBMS returns rows will probably change and thus the results will vary between calls. May be that's obvious, just wanted to make sure that this is not overlooked. Cheers, Fritz -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker +41 62 775 9900 (switch board) Aarweg 15 +41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
