Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index



On 10 Mar 2016, at 10:37 PM, Wols Lists <antlists@youngman.org.uk> wrote:

Well, all modern Picks implement SQL access.

And as far as I'm aware, all modern RDBMS implement some form of stored
procedure, ie have some form of internal programming language. I suspect
end users will find the Pick way of dealing with it is a lot easier than
the relational way, but hey, give them the choice!

And it would be nice to include an "easy to use" database with LO. imho
that means "something that is NOT relational"! Why do most people use
Excel instead of Access? Because Access is too hard!

The issue isn’t whether we support Pick, the issue is about how do we get out unit tests working 
for Base. 

Firebird was chosen some time ago because it supports SQL. Pick sounds great, don’t get me wrong, 
but I don’t think it’s a candidate for our automated tests, at least at this point. 

Chris

P.S. as an aside, when I was in high school, some wit printed a sign and stuck it to the high 
school computing teacher’s office door - it had a clipart picture of a PC and under it the sign 
read:

“What is G.I.R.L.S, and is it IBM compatible?”

Imagine my surprise to read the following on that Wikipedia article about Pick:

"Pick was originally implemented as the Generalized Information Retrieval Language System (GIRLS) 
on an IBM System/360”. I guess the answer was “yes”.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.