Skip to main content
C
cf_matt
Known Participant
March 25, 2008
Question

Form Builder storing results as WDDX

  • March 25, 2008
  • 11 replies
  • 1693 views
A while back i wrote a form builder. To store the results of a form submission I decided to use wddx and save the xml string into the db, which seemed like a good idea at the time. Further down the line this form builder has been used for much larger forms and sheer amount of data being store as text is making the server crash when it has to be serialized or deserialized.
I was wondering if there is a better way to store this data, obviously storing the data in tables would be a bit of a pain as the form builder is dynamic and can have any number of fields.
I decided against storing the wddx data in a text file as i was worried about read/write locks on a busy form. Was i wrong to go down this route?

Hope someone can help

Matt
This topic has been closed for replies.

11 replies

Show previous replies
N
Newsgroup_User
Inspiring
March 25, 2008
cf_matt wrote:
> I decided against storing the wddx data in a text file as i was worried about
> read/write locks on a busy form. Was i wrong to go down this route?
>
> Hope someone can help
>
> Matt

How are you storing the data? In varChar fields? If so could you
consider a CLOB (Character Large OBject) field? Assuming your database
management system supports them. This is somewhat like storing as a
text file, but your database takes care of managing them for you. It
improves the performance of your database tables which can ignore this
large data when it is not needed at the slight cost of not being able to
do normal searches and filters on any data contained in a CLOB field.
But I presume you are not doing any matches or filters based on this
data, are you?



C
cf_mattAuthor
Known Participant
March 25, 2008
Ian
I am storing using CLOB.
Basically when a person on the site fills in a form i have to append the row to the wddx packet, also when deleting rows i have to a cfquery and exclude the row that is to be deleted. There is a lot of going back and forth serializing and deserializing which seems to be creating a bottleneck on large amounts of data.

Oguz
Its storing the results from forms i'm having trouble with, i dont think i understand your solution or we have our wires crossed?
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices