I suppose there is nothing inherently wrong with it, just a seeming lack of
elegance. The link is intended to pass information (cat_id) to a query on the
next page, thus deciding from which category items should be listed.
Thinking about it further, I do have a third option. I realized that I can
simply append the query to read:
$query = "SELECT * FROM food WHERE ".$_SERVER[QUERY_STRING];
What are your opinions on that option? I am not terribly fond of it because it
allows for no scalability. I am a big believer in developing re-usable code and
this example seems quite limited. Thanks again.
Edward Dudlik
Becoming Digital
www.becomingdigital.com
----- Original Message -----
From: "Jason Wong" <php-db@gremlins.biz>
To: <php-db@lists.php.net>
Sent: Tuesday, 27 May, 2003 04:31
Subject: Re: Passing data between pages
On Tuesday 27 May 2003 16:24, Becoming Digital wrote:
> I have a simple script that creates a series of links based on the results
> of a query. As you can see from the code below, I am currently appending
> the query info to the URL, but I don't believe this to be an ideal
> solution.
There is nothing inherently wrong with that. Why do you believe it's not ideal
and what problem are you trying to solve?
--
Jason Wong -> Gremlins Associates -> www.gremlins.biz
Open Source Software Systems Integrators
* Web Design & Hosting * Internet & Intranet Applications Development *
------------------------------------------
Search the list archives before you post
http://marc.theaimsgroup.com/?l=php-db
------------------------------------------
/*
By trying we can easily learn to endure adversity. Another man's, I mean.
-- Mark Twain
*/
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
