On Thu, 14 Jun 2001, Leo Lapworth (on topic, for a change) wrote:
> XML - do it because you need it, not because of the Buzz.
Indeed ;-)
> XML is cool for handeling complex (or varied) data and sharing
> this info with others (but if CSV will do, then use that!).
I'll soon be implementing an
On Thu, Jun 14, 2001 at 10:44:50AM +0100, Jonathan Peterson wrote:
> At 10:01 14/06/01 +0100, you wrote:
> >The data from these files will primarily be diplayed within an HTML page.
> >A
> >perceived advantage of XML here (for someone who has barely scratched the
> >surface of what XML can do), i
At 10:01 14/06/01 +0100, you wrote:
>I could produce my own file format from scratch - and write the tools to
>look after it... eg
>
>#URL#http://whatever.com
>#SCORE#0
>#SUMMARY#'broken html' bugger"
When I see something like that I think it should be in XML. There's an
overhead involved with
From: Robert Thompson <[EMAIL PROTECTED]>
Sent: Thursday, June 14, 2001 9:25 AM
> Sorry to go off topic...
>
> I was wondering what the pro's and con's are of using XML to structure
ASCII
> based data files.
>
> What are peoples experience of using XML - particularly where you may have
> to tra
> Sounds like you need DBD::CSV.
Note to self... read all replies in a thread to make sure you don't
provide redundant information.
> CSV is an option - except that an awful lot of the data will need to be
> escaped out before it goes into the file, and I would rather only have to do
> when its rendered out to the browser.
> Unfortunately I'm not allowed to make use of the database - it is a
> requirement that this particular
> > From: Leo Lapworth [mailto:[EMAIL PROTECTED]]
> >
> > XML - do it because you need it, not because of the Buzz.
Amen.
>I'm also trying to future proof the system slightly - I think that by
>having the data XML based it may make it easier to use in new and
>wonderful ways in the future, wit
On Thu, Jun 14, 2001 at 11:19:10AM +0200, Philip Newton wrote:
> Roger Burton West wrote:
> > DBD::CSV is your friend.
>
> I second that. DBD::CSV is yum. Also handles escaping of double quotes or
> commas when inserting strings, etc.
Of course, the plain ol' CSV modules handle all the appropria
> From: Philip Newton [mailto:[EMAIL PROTECTED]]
> Roger Burton West wrote:
> > DBD::CSV is your friend.
>
> I second that. DBD::CSV is yum. Also handles escaping of
> double quotes or
> commas when inserting strings, etc.
DBD:CSV seems to be popular and on reading the docs I can see why...
..
Roger Burton West wrote:
> DBD::CSV is your friend.
I second that. DBD::CSV is yum. Also handles escaping of double quotes or
commas when inserting strings, etc.
Cheers,
Philip
--
Philip Newton <[EMAIL PROTECTED]>
All opinions are my own, not my employer's.
If you're not part of the solution, y
On or about Thu, Jun 14, 2001 at 10:01:33AM +0100, Robert Thompson typed:
>CSV is an option - except that an awful lot of the data will need to be
>escaped out before it goes into the file, and I would rather only have to do
>when its rendered out to the browser.
DBD::CSV is your friend. Sits on
> From: Leo Lapworth [mailto:[EMAIL PROTECTED]]
>
> XML - do it because you need it, not because of the Buzz.
Never was one for following the hype - just trying to work out if it's the
right tool or not.
Part of the problem is probably that I've heard snippets of what XML can
do/is good for, an
XML - do it because you need it, not because of the Buzz.
XML is cool for handeling complex (or varied) data and sharing
this info with others (but if CSV will do, then use that!).
I'd suggest it VERY much depends on why you want to use it,
what is the ASCII data ?
If it was worth putting the d
13 matches
Mail list logo
