巨大的平面文件 [英] humongous flat file

问题描述

有人建议，不要将已经很大的平面

文件（包含许多类似的行）转换为XML，而是将某些类型的标题附加到文件中$ / b $ b ，包含后面的行

的某种元XML描述。希望结果不会像

纯XML文件一样大，但仍然很容易交换。多个供应商将继续能够轻松跟踪格式更改。没有XML的平面

文件的大小已经是一个问题了。


如果还不是很明显，我是XML的新手。有这样的事情

已经存在吗？谢谢。


Dennis Farr

Treefrog企业


- 长颈鹿可以游泳吗？ -

It has been suggested that rather than convert an already large flat
file, with many similar rows, to XML, some type of header be attached
to the file, containing some sort of meta-XML description of the rows
that follow. The hope is that the result will not grow as large as a
pure XML file, but still be easy to exchange. Multiple vendors would
still be able to track format changes easily. The size of the flat
file, without XML, is already an issue.

If it is not already apparent, I''m new to XML. Does anything like this
already exist? Thanks.

Dennis Farr
Treefrog Enterprises

-- "Can giraffes swim?" --

推荐答案

2003年8月7日07:39:57 -0700， df *** @ comcast.net （Dennis Farr）写道：

On 7 Aug 2003 07:39:57 -0700, df***@comcast.net (Dennis Farr) wrote:

如果还不是很明显，我是XML的新手。这样的事情是否已经存在？谢谢。

If it is not already apparent, I''m new to XML. Does anything like this
already exist? Thanks.

这是一个坏主意，不要这样做。这些想法在最后一个世纪流行，当时的详细程度 XML被视为一个问题。


不是。克服它。

如果你想做XML，那就去做吧。这不是火箭科学。


不要发明一些新的伪XML协议来修复那些没有b $ b的问题。


如果你讨厌XML，那就这么说吧。享受你的打卡。

It''s a bad idea, don''t do it. These ideas were popular in the last
century, when the "verbosity" of XML was seen as a problem.

It isn''t. get over it.
If you want to do XML, then do it. It''s not rocket science.

Don''t invent some whacko new pseudo-XML protocol to fix problems that
aren''t there.

If you hate XML, then just say so. Enjoy your punch cards.

Dennis Farr < DF *** @ comcast.net>在消息中写道

news：c9 ************************** @ posting.google.c om ...

"Dennis Farr" <df***@comcast.net> wrote in message
news:c9**************************@posting.google.c om...

有人建议，不要将已经很大的平面文件（包含许多类似的行）转换为XML，而是将某种类型的标题附加到文件中，包含一些随后的行的元XML描述。希望结果不会像纯XML文件一样大，但仍然易于交换。多个供应商仍然可以轻松跟踪格式更改。没有XML的平面文件的大小已经成为一个问题。

如果还不是很明显，我是XML的新手。这样的事情是否已经存在？谢谢。

Dennis Farr
Treefrog企业

- 长颈鹿可以游泳吗？ -

It has been suggested that rather than convert an already large flat
file, with many similar rows, to XML, some type of header be attached
to the file, containing some sort of meta-XML description of the rows
that follow. The hope is that the result will not grow as large as a
pure XML file, but still be easy to exchange. Multiple vendors would
still be able to track format changes easily. The size of the flat
file, without XML, is already an issue.

If it is not already apparent, I''m new to XML. Does anything like this
already exist? Thanks.

Dennis Farr
Treefrog Enterprises

-- "Can giraffes swim?" --

如果您的平面文件包含固定长度记录且数据是文本的那么

您可能已经存在冗余尾随空格的现有开销。

这些空格不会被转移到XML文件，因此您可能会有大量的文件大小或者文件大小的显着减少。例如，< CustomersSurname>中的XML标记名称不需要过于冗长。标签可以

减少到< CS>只要你保持独特性。描述性标签名称与存储数据无关。
。最终应用程序可以提供罗嗦的

描述。


Denis

If your flat file contains fixed length records and the data is textual then
you may already have existing overheads with redundant trailing spaces.
These spaces would not be carried over to the XML file, hence you may have a
large or some significant reduction in file size. There is no need to be
overly verbose in your XML tag names for instance <CustomersSurname> tag can
be reduced to <CS> as long as you keep uniqueness. Descriptive tag names are
irrelevant to storing the data. An end application can provide the wordy
descriptives.

Denis

" Denis Saunders" <德************ @ norcross.com.au>在消息新闻中写道：< bg ********* @ au-nws-0001.flow.com.au> ...

"Denis Saunders" <de************@norcross.com.au> wrote in message news:<bg*********@au-nws-0001.flow.com.au>...

如果你的平面文件包含固定长度的记录，数据是文本的然后
你可能已经有冗余尾随空格的现有开销。
这些空间不会被转移到XML文件，因此你可能有一个大的或一些显着的减少在文件大小。例如，< CustomersSurname>中的XML标记名称不需要过于冗长。标签可以缩减为< CS>只要你保持独特性。描述性标签名称与存储数据无关。最终应用程序可以提供罗嗦的描述。

Denis

If your flat file contains fixed length records and the data is textual then
you may already have existing overheads with redundant trailing spaces.
These spaces would not be carried over to the XML file, hence you may have a
large or some significant reduction in file size. There is no need to be
overly verbose in your XML tag names for instance <CustomersSurname> tag can
be reduced to <CS> as long as you keep uniqueness. Descriptive tag names are
irrelevant to storing the data. An end application can provide the wordy
descriptives.

Denis

谢谢。我的数据文件是来自几个数据库

表的行的混合，并且大多数情况下没有空格但是数十个
（大多数是短的和固定的长度和编码的）每个表的列，所以

最短标记名称至少会使文件大小加倍。


给出类似XML的骨架会很不错对于文件顶部的每种类型的

数据库行，然后只需将记录标记为

它们来自哪个表，然后使用相应的骨架

来解析标签中的文本。每种类型的数千行可能有数千到数十美元，所以如果我们可以做到这一点，那么节省的大小将是相当可观的，如果有办法可以这样做并且

保持在既定标准之内，这将使我的一天。


我知道抱怨存储空间有点石器时代，但是

取决于应用程序的详细信息，并且大小翻两倍大小的文件可能仍然很昂贵。大小也会影响传输时间，特别是涉及加密时。我不是在敲XML，我希望让XML对更多人更有吸引力。

Thanks. My data files are a mixture of rows from several database
tables and for the most part there is no white space but tens of
(mostly short and fixed length and encoded) columns per table, so the
shortest tag names would at least double the size of the file.

It would be nice to give an XML-like skeleton for each type of
database row at the top of the file, and then just tag the records as
to which table they come from, and then use the appropriate skeleton
to parse the text in the tag. There may be thousands to tens of
thousands of rows of each type, so the size savings would be
considerable if we could do this, and if there is a way to do this and
stay within established standards, that would make my day.

I know it is a bit stone-age to complain about storage space, but that
depends on the details of the applications, and quadrupling the size
of a really large file can still be expensive. Size also affects
transmission time, especially if encryption is involved. I''m not
knocking XML, I''m hoping to make XML more attractive to more people.

这篇关于巨大的平面文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！