[600MRG] WSPRnet database

[Larry]

On 31-Oct-14 1:05 AM, microcode at zoho.com wrote:
>
> No, as far as I saw in my testing, OO has the same 1 mega-record limit as
> the other utilities we've been talking about. That's why I suggested
> sqlite. If you want to do ad-hoc queries it's perfect. If you can find a GUI
> it will make life much simpler for individuals. If there is a web-enablement
> add-on then it can serve the same role as suggested to be filled by SQL
> server, but be much easier to set up and lighter on resources.
>
> Even if not, it would be much easier for individuals to download a single
> sqlite database that works on every platform that contains everything and is
> manageable without slicing and dicing. As it is with the CSV much additional
> processing is required before you can even get started looking at what you
> want. The problem with Excel and OO etc. is not the monthly size it is a
> general problem of your query returning more than one mega rows.
>


I don't think I understand exactly what you are trying to tell me.

Yes, 64 bit implementations of Open Office and Microsoft Office have a 1 
mega row limit (32 bit implementations much less). That's a given and 
the reason this discussion started.

But by using the "grep" and/or "find" commands, we can pre-process the 6 
mega row monthly file and strip out the 630 meter data leaving us with a 
CSV file with only a half million rows, well within the 1 mega row limit.

Are you suggesting that the spreadsheet sort/count process will add rows 
and increase the data size beyond the application limits? That's not the 
process I envisioned but maybe it is necessary with the bloated 
inefficient applications we have these days.

My experience goes back to the days of DB3 and Lotus 1-2-3. I have done 
no programming at all since windows took over the world and very little 
EXCEL work. If fact I have done nothing since retiring 13 years ago and 
doing a full brain dump on the way out the door. Hence the reason why I 
am struggling with all this.

I agree that using SQL of some sort (SQLite, MySQL, etc) would be the 
correct way to do the analysis. But very few of us 630 meter guys have 
the resources to pull that off and those that do are seemingly not 
willing to get involved. I for sure can not spend the time and effort 
required to learn all this (or re-learn as the case may be) and won't 
even consider installing all this database stuff on my desktop.

So, as far as I can see, if it's not able to be done on a desktop 
spreadsheet, it is not going to be done at all.

73,

Larry - W7IUV / WH2XGP