Multiple Databases, Multiple Queries

mramonster

Right now I'm using a basic IF >>> Get to query my databases. However, I know there is a limit on 9 things you can query at a time and that using dozens of 'IFs' will slow down the search greatly.

if(isset($_GET['page']))
{
	$pageNum = $_GET['page'];
}

Is there a better and/or smarter way of doing this? Kind of alike a "catch-all" page in the possible query of all things?

bretticus

However, I know there is a limit on 9 things you can query at a time and that using dozens of 'IFs' will slow down the search greatly.

Are you building an SQL query string with the if statements? Your example IF just shows you setting a variable on a condition of another $_GET super global value. Shouldn't have anything to do with the final SQL query if you are building query to send to your database (dunno, not enough info.)

Also, are you saying you can send just 9 individual queries at once? Where does this rule of 9 come from? Just curious.

mramonster

Sorry I should've worded it better/correctly. What I meant was 9 different variables and the 9 comes from a rewrite point of view. As far as I know it will only allow you to do up to 9.

RewriteRule url-(.*)-(.*)-(.*)-(.*)-(.*)-(.*)-(.*)-(.*)-(.*)-(.*)\.html page.php?var1=$1&var2=$2&var3=$3&var4=$4&var5=$5&var6=$6&var7=$7&var8=$8&var9=$9

I have an event's site and right now I have several different pages for different variables such as events by week, events by state and so on. Basically I want to know if I should do a form and string together a bunch of Ifs to get all the lists of data or if there is a better/faster way.

Krik

Are you sending actual data via $GET? If so use $POST it is much easier.

Of course based on your example in your first post it looks more like a switch that will dictate what data in is shown.

And to have 9 or more of them makes me think the user is dictating the various switches and hence they are likely in a form which could easily sumbit via $_POST.

Is there a reason why you have to send it via $_GET?

laserlight

The rules of thumb for using get and post are:

The "get" method should be used when the form is idempotent (i.e., causes no side-effects). Many database searches have no visible side-effects and make ideal applications for the "get" method.

If the service associated with the processing of a form causes side effects (for example, if the form modifies a database or subscription to a service), the "post" method should be used.

bretticus

I think I have to say I'm with kirk, what's the point of doing a complex url rewrite when you could just send unlimited post vars from your form?

bretticus

I suppose, if you have, say, a hierarchical data-driven web site for displaying information about the events, you may want to rely on GET (as laserlight points out.) However, I've always been a fan of the fake directory structure instead. I'll illustrate with some quick code.

Apache or .htaccess config to force php parsing on a script called info...

<IfModule mod_php5.c>
<Files "info">
ForceType application/x-httpd-php
</Files>
</IfModule>

Then sya I have a url like http://mywebsite.com/info/beverly_hills/ca/stool

I can get the information in my info script like this:

define("REQUEST_CITY", 1);
define("REQUEST_STATE", 2);
define("REQUEST_ITEM", 3);

$params = explode("/", $_SERVER['REQUEST_URI']);

$city = $params[REQUEST_CITY];
$state = $params[REQUEST_STATE];
$item = $params[REQUEST_ITEM];

The benefit is that I can stick as many fake folders as needed to the urls. The downside is that all parameters have to occupy an ordinal spot.

There are many variations to this example. For instance, you could use list() to get the parameters or you could put "keys" in your folder names like: http://mywebsite.com/info/city-beverly_hills/state-ca/item-stool and delimit each pair on the hyphen (might as well use query strings at this point though.)

Again though, if you have need of more than 9, this sounds like a form and not so much a hierarchical data-driven web site. The only real benefit to the "fake folders" approach is that your details pages are exportable (ppl can send a link to their friend, etc. Oh and search engines can index them.)

mramonster

bretticus;10882395 wrote:
The benefit is that I can stick as many fake folders as needed to the urls. The downside is that all parameters have to occupy an ordinal spot.
Again though, if you have need of more than 9, this sounds like a form and not so much a hierarchical data-driven web site. The only real benefit to the "fake folders" approach is that your details pages are exportable (ppl can send a link to their friend, etc. Oh and search engines can index them.)

That is exactly the point. We get a lot of our Search Engine Traffic due to having lots of particular events indexed. So basically I will have to keep it down to 9 variables and should use GET (although POST is easier) so that way I can do URL rewrites, correct?

Thanks for all the information thus far guys! I really appreciate it!😃

bretticus

mramonster;10882614 wrote:
That is exactly the point. We get a lot of our Search Engine Traffic due to having lots of particular events indexed.

I should point out that the search engine indexing is only relevant if you have links on your page (with all 9 variables in the link to get to that detail page or hierarchical linking that that gets you there eventually.) They cannot index a form that you require to be filled out.

mramonster;10882614 wrote:
So basically I will have to keep it down to 9 variables and should use GET (although POST is easier) so that way I can do URL rewrites, correct?

Yes, if you are going to use rewrites, but again, you don't have to "Fence yourself in" with the url rewrite. IF, you need more, you can use my preferred method (forced file php parsing.)

I guess the question, for once and all, are you submitting forms or linking to pages?

mramonster

I'm linking to pages. Basically what we do is have a list of all the events with minimal details such as start date, end date, city/state and title. When you click on the Title it then brings up the event by itself and gives additional information for that event. right now it's all being done manually through HTML and I'm working on converting it all to Databases and PhP. So I'm trying to figure out the most user and SOE friendly way while being very structured and functional.

The form idea came about so a user could get a list from multiple states and/or cities and start/end dates. Also we're not just doing one trype of event so also querying those.

As of right now I have the single events set up, as well as single states and dates worked out using GET.

After mulling over this some more I believe that using GET is good for what I've got going, and then using POST for the form. This way I'd have all the Lists and Events indexed and have a very friendly User Form.

With that said which is the best way to POST? Using the HTML version 'echo'd or the PhP cURL?