Results 1 to 5 of 5

Thread: To use an XML file in order to store temporary data

  1. #1

    Thread Starter
    Lively Member
    Join Date
    Feb 2004
    Location
    Barcelona
    Posts
    70

    To use an XML file in order to store temporary data

    Is it a good idea to use an XML file in order to store temporary data until these data is correct, and then do the insert into the definitive DB?

    My exact issue is: I have three form pages registration process, if the user decides going back while he/she is in the form number two, I want to store the data entered in this second form in a temporary place in order to refill the form fields when she/he returns to the this second form, but I don’ t want to use Session State. I make the inserts on every form page and I only use Session to store the user id and a little few things more. On the other hand I can’ t use a normal DB insert (in this case that the user goes back without completing the form two) because this second form will be incomplete surely, and server validations would force the user to complete all the second form to be able to go back to the previous form page, and I don’ t want this. So, Is it a good idea to use an XML file in order to store these temporary (and maybe wrong) data? Only to refill the second form fields when she/he returns?

    I want to avoid too much data in session state, because many users at the same time storing data on it consumes much server memory. And many times there are alternatives much more faster and reliable.

    Thank you,
    Cesar

  2. #2
    PowerPoster hellswraith's Avatar
    Join Date
    Jul 2002
    Location
    Washington St.
    Posts
    2,464
    Create a denormalized table that holds entry until complete, then transfer that completed record to the real tables in the db.

  3. #3

    Thread Starter
    Lively Member
    Join Date
    Feb 2004
    Location
    Barcelona
    Posts
    70
    Hi hellswraith,

    What is a denormalized table? Maybe is it a normal DB table but in this case will be only temporal and without ‘rules’?

    Do you think that this practice will have better performance (faster and reliable) than storing data in session state?

    Thanks

  4. #4
    PowerPoster hellswraith's Avatar
    Join Date
    Jul 2002
    Location
    Washington St.
    Posts
    2,464
    I am like you, I don't like session state. I tend to store things in the database. Your definition of the denormalized table is correct. It is a normal table, but without constraints attached to it.

    Another idea: If there are not a whole lot of values to be stored, you could store them in a cookie.

  5. #5

    Thread Starter
    Lively Member
    Join Date
    Feb 2004
    Location
    Barcelona
    Posts
    70
    Ok , thank you very much hellswraith !

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width