I have not used temporary tables in recent versions of Links, so it might not work as expected, using the higher level calls, but here is a nice book excerpt on it (see the bottom of the article for the .pdf link)
http://dev.mysql.com/...l-db-design-ch5.html
You can also check the MySQL docs (http://mysql.org) for temporary table and get some extra quirks/bugs.
or here,
http://dev.mysql.com/...en/create-table.html
in the create table page.
Temporary tables _should_ work, since MySQL actually uses them internally for complex selects, so the "user session" should not be maintained beyond script iterations in Glinks (that's my only concern here).
Take a look at that short doc, above, and if you still have questions, I'll try to come up with some code later on, but it won't be until I'm awake, and that usually doesn't occur until well after dinner time for most people :{
But this is also where tricky caching can come into play. If you then query the database, for each of the available pages, (assuming there are 2 or 3) then stuff that result into a cache, when the user requests the next page, you check the cache first, then return the data, without re-doing the select/insert/select process. In exchange for a bit of disk space, you can cut repeat queries like this by thinking ahead.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
http://dev.mysql.com/...l-db-design-ch5.html
You can also check the MySQL docs (http://mysql.org) for temporary table and get some extra quirks/bugs.
or here,
http://dev.mysql.com/...en/create-table.html
in the create table page.
Temporary tables _should_ work, since MySQL actually uses them internally for complex selects, so the "user session" should not be maintained beyond script iterations in Glinks (that's my only concern here).
Take a look at that short doc, above, and if you still have questions, I'll try to come up with some code later on, but it won't be until I'm awake, and that usually doesn't occur until well after dinner time for most people :{
But this is also where tricky caching can come into play. If you then query the database, for each of the available pages, (assuming there are 2 or 3) then stuff that result into a cache, when the user requests the next page, you check the cache first, then return the data, without re-doing the select/insert/select process. In exchange for a bit of disk space, you can cut repeat queries like this by thinking ahead.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
