Wow I'd be really surprised if cfhttp was quicker than cffile.
Oddly enough, sometimes it is, when used to fetch a file from the local
machine. I was very surprised by that myself, as it strikes me as
counterintuitive, to say the least.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
isn't always desirable.
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Monday, October 13, 2003 8:32 AM
To: CF-Talk
Subject: RE: Storing XML
Wow I'd be really surprised if cfhttp was quicker than cffile.
Oddly enough, sometimes it is, when used to fetch a file from
Hi all:
What's an efficient way to store/retrieve XML other than a database
(let's assume I don't have access to one for now) ?
Now, I've tried CFFILE/write to throw down and CFHTTP to pull back from
the local web folders (seems to be quicker than CFFILE/read), but I've
gotta say, even on
Subject: Storing XML
Hi all:
What's an efficient way to store/retrieve XML other than a database
(let's assume I don't have access to one for now) ?
Now, I've tried CFFILE/write to throw down and CFHTTP to pull back from
the local web folders (seems to be quicker than CFFILE/read), but I've
gotta say
Hi there,
If you are still wishing to go down the route of XML after the previous posts, you
might wish to externatize some specific nodes in your XML data. That way the value of
particular nodes and particular atttributes are stored seperate from the XML in
another table with the ID of the
Somewhat OT but this is for a CF app and I thought it could be useful for
others too.
I'm in the processing of making a very flexible OO inventory app. The basic
rundown is this.
You have a table in the DB called Products. This is where you inventory
goes. Now because this database is going
Issac more or less covered why im using wddx. Because its so simple.
You can with with one statement, convert a struct to wddx, and wddx to a struct. You
cant get any easier than that.
The reasion i chose to store attributes in this manor was for flexibilty and
expandability. This is for an
Somewhat OT but this is for a CF app and I thought it could be useful for
others too.
I'm in the processing of making a very flexible OO inventory app. The basic
rundown is this.
You have a table in the DB called Products. This is where you inventory
goes. Now because this database is going
Instead I want to store the data as XML in a text field. Pretty simple
right?
I format the data using cfwddx. This way I can easily format the data as
it
comes in and out of the database. It works great.
But now I ran into a problem. What if I want to search by model? Say I
want
all the
Hi there,
If you are still wishing to go down the route of XML after the previous posts, you
might wish to externatize some specific nodes in your XML data. That way the value of
particular nodes and particular atttributes are stored seperate from the XML in
another table with the ID of the
You may check some native XML database, like Tamino or Xindice but,
sincerely I never used them, only read something
You may start reading from here:
http://xml.apache.org/xindice/
Massimo
~|
Archives:
Issac more or less covered why im using wddx. Because its so simple.
You can with with one statement, convert a struct to wddx, and wddx to a struct. You
cant get any easier than that.
The reasion i chose to store attributes in this manor was for flexibilty and
expandability. This is for an
to. columnar format, with some keys and good
design in mind.
tony
-Original Message-
From: Kwang Suh [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 10:30 PM
To: CF-Talk
Subject: Re: storing xml in sql
1) Using wddx is, well, a really bad idea. How can you describe a
product
using
,
but just to give you an idea.
2) Storing XML in a text field is, well, a bad idea.
Besides the obvious performance implications, you're
already running into problems with having multiple
pieces of data glommed into a big field.
That's not _necessarily_ true. If you do a good job
Issac more or less covered why im using wddx. Because its so simple.
You can with with one statement, convert a struct to wddx, and wddx to a struct. You
cant get any easier than that.
The reasion i chose to store attributes in this manor was for flexibilty and
expandability. This is for an
On Wednesday 20 Aug 2003 22:27 pm, Alan Quinlan wrote:
Instead I want to store the data as XML in a text field. Pretty simple
right?
Use an XML database, or one that supports a native XML type, such as Oracle.
--
Tom Chiverton (sorry 'bout sig.)
Advanced ColdFusion Programmer
Tel: +44(0)1749
Hi there,
If you are still wishing to go down the route of XML after the previous posts, you
might wish to externatize some specific nodes in your XML data. That way the value of
particular nodes and particular atttributes are stored seperate from the XML in
another table with the ID of the
Im working on something with the best of both worlds i think. I
basically made a product_attributes table that links to the product
table. All the attribtues can go there. Its not what i originally
wanted to do, but im meeting myself in the middle here. hah
Hi Alan,
I would recommend this last
Somewhat OT but this is for a CF app and I thought it could be useful for
others too.
I'm in the processing of making a very flexible OO inventory app. The basic
rundown is this.
You have a table in the DB called Products. This is where you inventory
goes. Now because this database is going
1) Using wddx is, well, a really bad idea. How can you describe a product
using wddx?
2) Storing XML in a text field is, well, a bad idea. Besides the obvious
performance implications, you're already running into problems with having
multiple pieces of data glommed into a big field.
Seems
20 matches
Mail list logo
