Would a TSB (Tab Separated Value) format be preferable? Full-stops
and commas are used in numbers as decimal and thousands separators (or
vice versa), so using tab character would avoid any problems with
commas in the actual data (and make it is a bit easier to quickly
eyeball when viewed in a
We have mountains of data here too. The best why to store it is in a
real database of some kind. There are several that are free, open
source and multi-platform. The best for this use is Postgres. As
this is free and open source there is no reason not to use it.
In the past I've kept
On Mon, Jan 10, 2011 at 2:08 PM, Bob Bownes bow...@gmail.com wrote:
There is a difference between archival format and database format. If you
are looking for an archival format that is portable, then a CSV (or other
delimiter of your choice) is ideal. They are easy to import to a real
database
measurement
Cc: scmcgr...@gmail.com
Subject: Re: [time-nuts] Archiving Timing Data
On Mon, Jan 10, 2011 at 2:08 PM, Bob Bownes bow...@gmail.com wrote:
There is a difference between archival format and database format. If you
are looking for an archival format that is portable, then a CSV (or other
You saved me a lot of typing. :) Comments inline...
--- On Mon, 1/10/11, Bob Bownes bow...@gmail.com wrote:
From: Bob Bownes bow...@gmail.com
Subject: Re: [time-nuts] Archiving Timing Data
To: scmcgr...@gmail.com, Discussion of precise time and frequency
measurement time-nuts@febo.com
Date
Hi
I'm sitting here running data on a bunch of TBolts and the like. Might that
data be useful to others - maybe. Could it be useful 100 years from not -
doubtful. I have the ability to create enormous amounts of likely useless
trivia. To me the burring the useful nugget in the mountain of
-To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Subject: Re: [time-nuts] Archiving Timing Data
Hi
I'm sitting here running data on a bunch of TBolts and the like. Might that
data be useful to others - maybe. Could it be useful 100 years from not -
doubtful. I
