Aaron Weiker wrote:
> For some reason I don't think this was understood of what I said earlier.
>
> THE "DATABASE" ISN'T RESPONSIBLE FOR XML
>
> But, just because the database isn't responsible doesn't mean that the
> application is responsible for generating XML.
>
> > to put this wrapper on MySQL to be able to send queries to and have the
> output be in XML. There is no problem with this, nor should there be months
> of debate on whether or not this is a database function because it's
> obviously not.
As was posted earlier ->
http://www.xml.com/pub/a/2000/12/13/perlxmldb.html
This is an example of doing that between Perl and MySQL. THis sit's
inbetween your application (In Perl in this case) and MySQL. Neither
your app, nor MySQL is responsible in itself for the formatting. The
RDBMS is only caring about the data itself, not it's format, and the
Perl code get's nicely packaged XML back in return. Just like the basic
Unix chaining on the command line. Each program should do it's job
well, and not something else's, if you want more done, just pipe them
together so it's much more re-usable.
Jayce^
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
