Re: Pick query languages compared to SQL


dawn wrote:

Agreed. My next entry will talk about one aspect of this. Some
features are

1) It is an extensible descriptive (rather than prescriptive) schema

Meaning that there may be missing or no dict items at all, leaving the
developer in a virtual minefield when choosing new attribute numbers to
add data.

2) You can create synonyms, or describe data with different
"conversions"

That can present the data inaccurately and leave one wondering which of
the 20 synonyms for an attribute is the "correct" one.

4) You can change a field from describing stored data to derived data
without changing queries.

So the results could change and the user is left wondering how/why?

You can change a field from single to
multi-valued or vice-versa without breaking queries.

Not likely true if your sort criteria is based on a single value field
that you change to multi-valued.

The dictionary approach gives much more flexibility
and power and I think is easier to comprehend and use.

Outside of creating columnar, printed reports that few people use these
days, GIRLS, Access, English, AQL, etc. seems to have very few, if any
real, advantages over SQL.

I would say one of the biggest disadvantages of AQL is the inabilty to
return a data set. You may have a wonderful set of dicts in a customer
file that has all sorts of neat translations and conversions, but when
it comes to using that information in a PICK BASIC program, the best
AQL can do for you is get you a set of keys. You must then write all
the code to access the various files to retrieve, display and/or update
that information

Also, outside of using the Pick EDitor, and UPdate processor - neither
of which should be unleased on the common end-user, the only way to
update information in MV files is via BASIC programs. The data
manipulation features of SQL are quite handy and certainly more
powerful than those available in AQL/GIRLS.

Note that I'm not advocating SQL over MV, I use both. I just tire of
the smugness I sometimes see among MV advocates who think MV is above
and beyond all else. MV has its share of warts too.

--
Kevin Powick

.

Relevant Pages

  • Re: Microfocus & Oracle data types
    ... Like you I am *NO* expert at SQL. ... Next one is me "Don't use Directives if you ... using features I'd forgotten I had included. ... So now I let the ESQL module generate my syntax - the text ...
    (comp.lang.cobol)
  • RE: problems with visual studio 2008 on vista
    ... Administrative utility to install and uninstall ASP.NET features on a SQL ... -d <database> Database name for use with application services. ... specify a database and ensure that the web.config file is modified ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: SSMS Invalid Handle Error On Install
    ... dependant features. ... I'm planning to uninstall SQL Server 2008 and run the Process Monitor. ... There is an issue with SQLPrompt where it can cause the SSMS installation ...
    (microsoft.public.sqlserver.tools)
  • Re: Fox is dead, long live the fox!
    ... There are, apparently, some exciting new features coming in Orcas (the next ... MCSD, Visual FoxPro MVP ... > .NET developers to run ANSI standard SQL queries on ADO ...
    (microsoft.public.fox.programmer.exchange)