The product will be stored in the database but all the versions
of it would be stored on the server in XML with the transactions
being recorded in it.
The database would be better suited to store the information than an XML
file unless you want to transmit that XML info without going to the
This type of data logging is quite common. One way to do it is before
doing the update, get the record again from the db. Compare it to the
form data. Another way is to have the form send a duplicate set of
form fields named something like orig_productName. Or you could even
be fancy with some
Hi, Phil...
I'm not experience with XML, just vaguely familiar with it, but I'm curious
as to why you're using XML as part of your process and not just interacting
with a database only.
Rick
-Original Message-
From: Phill B [mailto:[EMAIL PROTECTED]
Sent: Monday, April 07, 2008 11:40
The customer would like to have versions of the product that he could print
out. I'm not sure I see an easy way of doing this with the data stored like
this. Then again its Monday morning and I'm not firing on all cylinders yet.
:-\
On Mon, Apr 7, 2008 at 10:49 AM, Matt Williams [EMAIL
On Mon, Apr 7, 2008 at 11:05 AM, Phill B [EMAIL PROTECTED] wrote:
The customer would like to have versions of the product that he could print
out. I'm not sure I see an easy way of doing this with the data stored like
this. Then again its Monday morning and I'm not firing on all cylinders
The product will be stored in the database
but all the versions of it would be stored
on the server in XML with the transactions
being recorded in it.
Why not store that in the database? That's what databases are for. XML is
better for transport between systems, databases are better for
Hey Rick
The thought is that we could have an easy to access snap shot of the product
that would include a reference to the last edit.
Here is my idea behind the XML. Lets say I have the following XML (I hope it
comes thru)
product
nameCool Product/name
cost321/cost
/product
If Jerry
Very true. The problem I'm having is that I cant figure out how to do this
in a database. I've never worked with a database driven application that
stores revisions that I can dig through the code to see how they do it.
Plus, I couldn't find any good articles or books on this sort of thing.
That's
@sql
end
end
END
go
===
Regards
Richard
-Original Message-
From: Phill B [mailto:[EMAIL PROTECTED]
Sent: 07 April 2008 17:30
To: CF-Talk
Subject: Re: Can you guys give me your thoughts on this?
Very true
-Original Message-
From: Matt Williams [mailto:[EMAIL PROTECTED]
Sent: Monday, April 07, 2008 11:49 AM
To: CF-Talk
Subject: Re: Can you guys give me your thoughts on this?
This type of data logging is quite common. One way to do it is before
doing the update, get the record again
I do something similar, but I have date_added and date_removed columns
(each with a corresponding user column), so I know that if
date_removed IS NULL then I have the latest version of the record. It
provides full auditing in that we know when a record was added, when
it was removed and by whom.
11 matches
Mail list logo
