very slow to display

Yeah I admit it's slow to display, it's not optimized at all for large amounts of data. You see *every* time it creates a table view (I really mean *every* time, even for pagination - it has no caching at all) it loads the ENTIRE table into an array, it then sorts this array, then clips it to the paginated results it requires and then finally outputs it to the screen. So every time you click 'next page' it's doing this over and over again and that's a whole lot of work...

The reason it does it this way is because mysql is RUBBISH for sorting... Well, I mean it can sort - but you can't apply natural sorting which I require. There's another reason as well and I'm afraid it's because tablemanagers structure (currently) is pretty generic, meaning its not made to be specific for one table - it's generalised so that any table of any length containing whatever can be made using it. I'm afraid with this version there is no ideal solution? If I do it one way I appease people who have lots of rows, if I do it another way it's better for users who require natural sorting and well... I'm afraid as I mentioned above, I'm one of the people who require natural sorting and so you're pretty much stuck with how I want it done at the moment.

...There is however some light at the end of the tunnel. In the dev version of tablemanager (which is too dev at the moment to be available for download) tables are created as db tables and so are completely optimized for each specific table. This is a recent development as I assumed before that doing it this way would be frowned upon, but then I noticed that content_types are created this way and I thought... "Well if it's good enough for them..." so yes, that'll be coming along soon.

Pobster

--------------------------------------------
http://www.justgiving.com/paulmaddern
--------------------------------------------

Closing as D6.x is now unsupported.