jQuery Grid Plugin - jqGrid

Your original url:'new.php' handles both the  initial load and subsequent loads (includes the search parameters).

Use Firebug or some tool to see the 'filters' posted.

tim

I'll do my best, but I don't think I fully understand you.

> What i am failing to see is if both the display and the search is handled by in my case new.php then how are these filters reacting with the db?

The first post made for your grid to request data is on load and has the following argument:

_search  false

So you can use PHP or whatever to return your base set of data.

When you fill-out the search box and request filtered data, the new post args are different where 

_search    true
nd    1275596107133
page    1
rows    10
searchField    id
searchOper    eq
searchString    27
sidx    id
sord    desc

Knowing search is now true you need to use server side code (like PHP) to grab these arguments and use them to run a new SQL query that obtains the filtered data.

I'm no PHP guy, but the demo PHP example files typically store the results of the SQL query in a variable like $results, which is in turn echoed back as a response to the post, which then loads the new (and different data) into the grid.

> do i need to communicate with these files or are you saying that all display and search results should be as per my script above and search results should show?

Yes. Your new.php script needs to handle the arguments passed from the client and return filtered data should _search = true. 

One additional thing I notice is that you have mtype: 'POST'. I generally leave that out so the default is GET as it's intended to return a response.

[Edit] All this being said, if your intent is to send the data to the client once, then let them search within the already loaded data, then use  the new local data settings… I believe searching on large client side data is a new feature in 3.7 so you would need to check the docs for details.

tim

np.

> does the search need to be built into one these files?

The jqGrid plugin automatically applies the search parameters to your 'new.php',  so you don't need to specifiy a separate url for searching.

> in new.php as above, does that become new.php?q=1

some demo files have q=1 as part of the base url. So it's included in every request for data. Tony uses q=1 just to specify which base query he wants to run for a given grid example.

For you, new.php becomes new.php?searchField=id&searchOper=eq&searchString=27

so new.php will include your search.

> the way i see it, there is no other way to pass the values to say search.php as per the demo files

I'm not sure which example shows 'search.php', I see  'server.php?q=1' , but either way the url name is just a name, and jqGrid will use url:'xxxx.php' the same way no matter what the name is. For ease in understanding I always use 'data' in the url name since it better represents what it's purpose is.

ie. change 'new.php' to 'data.php' just to make life easier

tim

So look at your SQL statements:

$result = mysql_query("SELECT COUNT(*) AS count FROM jqgrid");

$SQL = "SELECT * FROM jqgrid ORDER BY $sidx $sord LIMIT $start , $limit";

and compare that to the jqGrid example:

$result = mysql_query("SELECT COUNT(*) AS count FROM invheader a, clients b WHERE a.client_id=b.client_id");

Yours has no WHERE clause.

You can see the arguments you need to check for:

$row[id],$row[title],$row[director],$row[year],$row[bond],$row[budget]

and you know how to check for them…

$id= $_GET["id"];

I'm not a php guy so I am not going to start debugging/suggesting your code, but you need to handle the arguments passed into your php script and incorporate them into your SQL statement.

tim

np