?

Log in

No account? Create an account

"XQuery will be worse, not better, than SQL."

« previous entry | next entry »
Aug. 5th, 2004 | 04:11 am
mood: awakeawake
music: Jose Alfredo Jimenez con Mariachi Vargas - Mexican Hat Dance

Finally someone explains how XML is crap using ideas I can understand. Interestingly, they shoot down SQL as well because it fails to implement the One True Relational Model.

This all sort of explains why my XML exposure has been like this: load up the XML file in a text editor or an IDE that runs slow as molasses (because it's working on a huge huge file of redundant text -- it's like running uncompiled code!), figure out an XSL transform to make it look like a set of MSAccess tables, and import them to Access. Now all the implicit things become explicit, and speedy, too. Ahh. Now we can ask the data what it means.

Link | Leave a comment |

Comments {9}

Aurifex

Sounds similar to some of my first impressions

from: aurifex
date: Aug. 5th, 2004 12:04 pm (UTC)
Link

But XML seems to be best implemented as a data transfer mechanism, not so much a data storage mechanism; and certainly not something that is meant to be manipulated directly on a regular basis.

Reply | Thread

Re: Sounds similar to some of my first impressions

from: nobodobodon
date: Aug. 5th, 2004 02:10 pm (UTC)
Link

Hammers are crap! (If you're trying to tighten screws.)

Reply | Parent | Thread

Triple Entendre

Re: Sounds similar to some of my first impressions

from: triple_entendre
date: Aug. 6th, 2004 05:59 am (UTC)
Link

"They look like nails to me! BAM!"

or...

"Hammers will solve all our problems because they're so cool! Is your solution hammer-compatible? Our product is better, because it supports hammers. What, tighten this screw? Hmm, screw-management systems are too complicated and don't represent our problem domain well! Our problem has a hammer, see? BAM! Ooh, that method seems to crash the screws. We are misapplying our hammer!"

"We need to work on a better hammer-based solution. How about if we attach this heavy oscillating motor to the hammer's base, and apply pressure slowly to the screw? See, it vibrates right into place! Hammers are an excellent framework for these sorts of problems."

"It's a bit slow on screws, but we're working on that. Here's a proposed query mechanism that should help: we'll attach this laser measuring device alongside the hammer head to vary the vibration speed depending on screw properties!"

Reply | Parent | Thread

Triple Entendre

"Best implemented as", yes. But -- should it be implemented at all?

from: triple_entendre
date: Aug. 6th, 2004 01:57 am (UTC)
Link

Except that XML is a good data transfer mechanism ONLY because it's easy for humans to read. (A trap I fell right into.)

My thoughts on this are incomplete.

Seems to me the advantages of XML are that you can validate it, but surely you could do that by having a schema for any arbitrary format, even a "binary" one.

Hmm, couldn't any binary data format be automatically translated into an XML file (which could then have a "proper" schema), as long as there was some repeated pattern (or you knew the format already)?

Taking it to the extreme,
Couldn't ANY sort of file be "decompiled" into XML?

Isn't XML therefore just a "pretty-printed" view of data?

Reply | Parent | Thread