Re: Using a Database within Windows + Dyalog APL

"jk" <*axy*@[EMAIL PROTECTED]
 (remove the asterisks)> wrote in news:480c679d$0
$25476$ba620dc5@[EMAIL PROTECTED]
> 
> "aleph0" <apl68000@[EMAIL PROTECTED]
> wrote in message 
>
news:820de252-ea05-4843-b7fa-d3a3f0ca2256@[EMAIL PROTECTED]
>>> ... and take 200 times overhead for granted
>>
>> Is it really "that" bad ?
>> .. say compared to MySQL.
> 
> that's like comparing 20 inches of snow with 21 
> 
> 

Gennelmen...

Are we having a self-destructive argument here?

There are good reasons for choosing to use either a "general" SQL-based 
database (MySQL, SQLite, DB2, and many others) or a roll-your-own data 
storage scheme.  The application and the context dictates.

I've achieved quite adequate performance interfacing from APL (and J) to a

variety of "standard" relational databases.

The point really is that it is quite easy for us to write applications in 
APL2, Dyalog, APLX or J (don't have any recent APL*PLUS/2000/Next 
experience) that can share their data with applications written in other 
languages - all the vendors have done a great job for us and we need to
get 
the message out that Jerry Turner put into his book title twenty years 
ago...

APL Is Easy!