Re: Ada package registry?

["Randy Brukardt" <randy@rrsoftware.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3444 bytes --]

"Björn Lundin" <b.f.lundin@gmail.com> wrote in message 
news:n95v9b$3hi$1@dont-email.me...
> On 2016-02-06 01:30, Randy Brukardt wrote:
...
>>> Yeah, having millions of records in .csv and
>>> joining with a couple of other .csv files with
>>> the same amount of data and
>>> sounds like a really good idea...
>>> If you got plenty of time, that is.
>>
>> Huh? You said that it is hard to pull data to Excel, and I disagreed. You
>> didn't say anything about pulling *all* of the data -- and why would you 
>> do
>> that? Excel would fall over if you gave it a million lines of anything - 
>> the
>> maximum number of rows is (or at least was) less than that.
>>
>> Obviously, you'd do the selection before exporting to Excel (the case I 
>> was
>> talking about).
>
> And that is the hard part. Of course you don't pull that kind of data
> into excel. But the selection itself  - into useful data from several
> sources - is hard using csv-files and ada.
> and no one in the business would be able to conclude anything
> useful from their own data.

You're still not making much sense. The Ada code would do the selections, of 
course; .csv would only be an export format. If you're exporting ALL of the 
data, something is wrong. Besides, when I say that DBs are overused, I 
surely don't mean that they have NO uses. If you have to do a lot of join 
selections and the like, you might very well need a DB. The problem is, a 
lot of the time people are using "join" when there is a better solution.

>>  > Looking at a customers trace table I see they generate about 100_000
>>> records a day. Order lines are around the same.
>>> Data saved for a month or two, before moving to long-term storage (db
>>> not connected to production)
>>
>> Way too much data -- 
>
> for csv-files : yes. for an RDBMS : no
> for business analysis : no.
> For tracking what store got delivery from what pallet : definitely no.
> And that is really important, if you find trouble in a batch of say
> food, and want to withdraw it from the stores. Which stores are affected?
> - Wait , I need to call an Ada-programmer to write a tool to extract
> that data from our many and BIG csv-files...

Big .csv files? Surely hope not. And as far as needing a programmer: of 
course, a programmer has to be involved somewhere. Whether that be Ada or 
SQL or Java, still need a programmer.

...
>> I *hope* they waste their time with fancy ERP systems rather than getting
>> anything done so they can go out of business faster... :-)
>
> A statement that I do not know what to think of.
> I see the smiley, but I don't see the fun in it.
> I do see it as fairly immature though.

Sorry, I made a political remark and mixed it into a technical discussion; 
too off-topic for here. But I will say that as someone who started a 
business and have some insight into day-to-day activities, the balancing act 
required for a small business to do right by their customers and 
employee/owners is very difficult. Once you throw in the disconnect of size 
and of outside owners, it becomes completely impossible. Smaller businesses 
are preferred, in part because failure *is* an option -- meaning no one is 
locked in.

I detest ERP systems for many reasons, but they seem to help clog up the 
works at many businesses that are better off being replaced by smaller 
versions anyway. So in that sense they are a positive... :-)

                                            Randy.