XML vs. SQL hmm.
It's worth recalling *one of* the rationales behind XML: When bytes
were expensive, machine to machine communication especially across
company boundaries (read EDI) couldn't afford to be self-documenting.
Huge binders of ANSI EDI specifications were required to correctly
You've all made great points and I'm sure that I'll follow the advice
given but I'll ask you to indulge me just a bit more.
Chris, you've almost convinced me, but I have to ask, is it really so
inefficient to search through one directory with 5000 sub-directories
to find one that matches the
On Feb 4, 2004, at 1:59 AM, Bill Stephenson wrote:
It occurs to me that the unix os is basically a database in and of
itself and perl interacts directly with the os, therefore, using it to
store and retrieve data may not be that inefficient.
I agree with this - you can get good results with a
Ian Ragsdale wrote:
On Feb 4, 2004, at 1:59 AM, Bill Stephenson wrote:
The above are some of the excuses I've come up with to avoid spending
more time learning stuff. If I'm deluded, it's because I have boxes
upon boxes of software that doesn't work anymore and time invested in
each of them.
I can give a longer reply later, but it's my birthday and I'm about to go
out for a late breakfast a movie :)
On Wed, 4 Feb 2004, Bill Stephenson wrote:
Chris, you've almost convinced me, but I have to ask, is it really so
inefficient to search through one directory with 5000
On Wed, 4 Feb 2004, Rick Measham wrote:
I'd love to see an XML parser embedded into SQL so that I can have:
CREATE TABLE aTable (id serial, data XML);
Does this help?
% mysqldump --help | grep -i ml
-X, --xml Dump a database as well formed XML.
% mysql --help | grep
If you're busy please forgive me and ignore this, if you have time to
offer an opinion I'd really like to hear from this list on this
subject;
If I am building a web app from the ground up, what's the best way to
deal with storing/retrieving data? For arguments sake let's say the app
will
On 4 Feb 2004, at 03:16 pm, Bill Stephenson wrote:
As computers keep getting faster, and memory and storage cheaper,
isn't it beneficial to program in the most simple, human readable,
least learning required, method?
Never. You're not going to ever read each 2500 user's 2000 x 40kb
records
On 4 Feb 2004, at 03:39 pm, kynan wrote:
The idea of having XML in the DB is sound though, if you do it
thoughtfully.
So long as you're not planning on searching on it or indexing it or ...
I once used XML to store information about a webpage as a PostGreSQL
field ... but later down the track I
On Tue, 3 Feb 2004, Bill Stephenson wrote:
If I am building a web app from the ground up, what's the best way to
deal with storing/retrieving data?
It's not by accident that databases have come to be popular for this kind
of work. Pick one -- MySQL, PostgreSQL, SQLite, or something real --
10 matches
Mail list logo
