CODEWITHSUNDEEP
c#asp.netpage-refresh
yahya kh
yahya kh

Reputation: 751

Refresh page repeat database transaction?

I have over 30 aspx pages, i have discovered a problem recently that if i did any kind of database transaction like insert, update, delete and then after the transaction is complete i pressed F5 or refreshed the page in anyway the same is transaction occur.

I searched for a solution but all i could found is that i have to check for viewstate on each button which is impossible, cause that means there will be a lot of work. There got to be generic solution, please help me in this problem.

Edit:

Here is the code on one of the buttons which change a value in data base to either true or false:

 protected void btn_Publish_Click(object sender, EventArgs e)
{

    if (Convert.ToBoolean(int.Parse(hf_Published.Value.ToString())))
    {
        publish(false);
    }
    else
    {
        publish(true);

    }

}

After the execution of the code if refreshed the page the same code is executed, i noticed that since a break point was placed on this method.

Upvotes: 0

Views: 1062

Answers (4)

Sunil Chavan
Sunil Chavan

Reputation: 524

You can try this. I used this in several project and working successfully.

 public bool IsRefreshed
    {
        get
        {
            if (Convert.ToString(Session["RefreshTimeStamp"]) == Convert.ToString(ViewState["RefreshTimeStamp"]))
            {
                Session["RefreshTimeStamp"] = HttpContext.Current.Server.UrlDecode(System.DateTime.Now.ToString());
                return false;
            }
            else
            {
                return true;
            }
        }
    }




protected override void OnPreRender(EventArgs e)
    {
        base.OnPreRender(e);
        ViewState["RefreshTimeStamp"] = Session["RefreshTimeStamp"];
    }



protected override void OnLoad(EventArgs e)
    {  

        if (!Page.IsPostBack)
        {
            Session["RefreshTimeStamp"] = HttpContext.Current.Server.UrlDecode(System.DateTime.Now.ToString());
        }
        base.OnLoad(e);
    }

Upvotes: 2

NSGaga
NSGaga

Reputation: 14302

Unless it's a real 'transaction' like payments etc. (which others already explained, do redirect etc.),
You could also try defining caching on your pages that interact with the Db or are bottlenecks for your app.
If you wanna have always live info (and it's that 'alive' type of app) then no luck with that solution (but even then), but usually, you can put some reasonable time expiration on how 'fresh' you want your data to be.
Caching ASP.NET Pages

Upvotes: 0

ionden
ionden

Reputation: 12776

To fix this issue you could check the following:

  1. Disable the submit button when necessary
  2. Add some validation to your code and check for double entries
  3. Redirect the user to another page after submit

Upvotes: 1

Wiktor Zychla
Wiktor Zychla

Reputation: 48230

There IS a generic solution, used for years by thousands of developers.

And the solution is: each time you perform an intrusive process at the server (insert/update/delete) you don't just render the page but rather you redirect the response with 302 to a fresh page with "your transaction succeeded" message.

This way, pressing the F5 will just refresh this message page, not the original page which triggers the transaction.

It is up to you whether or not this is directly applicable in your scenario.

http://en.wikipedia.org/wiki/Post/Redirect/Get

Upvotes: 2

Related Questions