Smarty

[weblink]

Hello,

I'm new to smarty and I've got problem with pagination when pass the data from one page to another. I need to encrypt the data while passing that one.

Here is my PHP code for setUrl....

[bimal]

As open_date and close_date do not seem to be associated with your paginator, you should encrypt your values within the php file, while assigning them.

For example,

[weblink]

Thank You for your reply bimal,

I tried with your solution with in php itself.

[jothirajan]

Yeap... Let me know whether you have good knowledge in creating PLUGINS in smarty if so please take a test here

1) Write the encryption code is PHP and pass in the browser
2) Write the decryption code in Smarty and get the values.


If this ok for you. Else i will post some more details.

TY
Jo

[bimal]

Hmm, it won't display your contents according to your virtual ID because it is encrypted.

You should decrypt this piece first, so that your virtual_id becomes a valid thing for you to continue.

Do not encrypt your IDs with one way encryptions like MD5, because you may need to decrypt it to the original value. However, there are multiple solutions as well. For each encrypted value, you should keep a record of its original value as well, probably in the database. So, while decrypting, you can get back the real virual id.

Thanks

[mohrt]

Pass those values through the PHP session on the server side, no need to encrypt them.

[weblink]

I don't have much knowledge about this topic, can anyone give the solution with example .

Thanks

[weblink]

Hi all,

I'm using a query to retrieve the from table and stored the result in an array.
If the user clicks on the submit button, then the retrieved from table in between the open & close dates. The result of the data will be stored in an array variable..assume $data_array variable.

[bimal]

When your data is too much, you should draw/select only the amount of data as your per-page's setting is, rather than pulling everything into a $data array.

In this case, say, your per-page (number of records per page) is 100, but your open/close date range contains 2000 data, then, you can have 20 pages: 1-...-20.

In whatever page you are, you should load only 100 records at once, for displaying your actual records in the page.

But for pagination, you should work differently - specially for identifying:
1. How many total records (and hence, page) are there in the page.
2. In which page number you are currently in.

By this, you should not draw 2000 records.

Other other easier way would be to use SQL_CALC_FOUND_ROWS: This saves a step in between. You should NOT use COUNT() in the sql to identify how many records are there under your conditions.

Here is an example:
SELECT SQL_CALC_FOUND_ROWS
data.column1,
data.column2
FROM data
WHERE
...
LIMIT $from_index, $per_page;

Then, immediately run: SELECT FOUND_ROWS() total; query to know how many records were there, when you did NOT use the LIMIT. This gives a number equivalent to your total number of records to paginate.

Please see the MySQL manual for SQL_CALC_FOUND_ROWS.
And, hopefully, it boosts up your operation speed several times.

Just remember, in whatever page number you are in, you are NOT going to pull records more than your $per_page configurations.

Thanks.

[weblink]

Hello Bimal,

I tried that you suggested. Actually i am having 7 Lakhs records in my table, with my query i am taking 50,000 records from this 7 Lakhs records. I got this 50,000 records in 40 seconds and each page displaying 500 records. I tried my query added with "LIMIT 0,500", then it takes around 34 seconds to retrieve 500 records.

Any other way to reduce the time for executing the query?

Thanks

[bimal]

Yes. There are ways to reduce the time used in SELECT query. You should better index your database, which can reduce an operation of around 10 minutes into few seconds - That was my case.

Importantly, indices should be case-based - you must see how you have written your SELECT query. Wrong indices will not improve the time.

In your case, you may too have to include your open/close date parts in your index as well. But this will be out of Smarty's forum here. But a quick way to create an index is:

[mohrt]