Cal Evans ([EMAIL PROTECTED]) writes:
> Top of the morning to ya Aaron,
>
> 1: Ed did not suggest that everyone has to have a CS degree. Not defending
> Ed because based on his posts this morning, someone pissed in his Cheerios
> but he simply stated that people should be a little more educated
Message-
From: Aaron Weiker [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 22, 2001 8:00 AM
To: 'Ed Carp'; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: RE: XML support under mySQL
For some reason I don't think this was understood of what I said earlier.
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 21, 2001 7:42 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: RE: XML support under mySQL
Mehalick, Richard RE SSI-GRAX ([EMAIL PROTECTED]) writes:
> Some relational databases return results in XML format.
An
Mehalick, Richard RE SSI-GRAX ([EMAIL PROTECTED]) writes:
> Some relational databases return results in XML format.
And operating systems have been written in Java and Perl. So? Just because you *can*
doesn't mean you *should*.
Suppose I want to translate the output to something else. Now I
Eric Frazier ([EMAIL PROTECTED]) writes:
> One thing I want. A Java way to save a data structure and recover it later.
> Easy in perl, not so easy in Java. But XML would be a great way to do it in
> Java.
Why Java? That's like going to a gas station and saying "I want gas specifically
formul
Aaron Weiker ([EMAIL PROTECTED]) writes:
> application interface. XML is this magic layer in the middle that each party
No it's not. XML is simply an emerging standard to describe metadata. No magic
involved.
> about to get this Email). The solution would be to have this other middle
> tier
Mehalick, Richard RE SSI-GRAX ([EMAIL PROTECTED]) writes:
> Another reason, maybe even a better one, is that XML is less database
> specific. So too will be the data. So the result of a query is no longer
> tied to the database that produced it.
Untrue. Data is data. The result of a query sh
