[Info-vax] VMS Software: New US Mailing Address

[Arne Vajhøj]

On 10/13/2022 9:18 PM, Bill Gunshannon wrote:
> On 10/13/22 19:14, Arne Vajhøj wrote:
>> MySQL/MariaDB - no pre-compilers
> 
> No one has expressed a need or desire for it yet.  (I have done
> some playing with making ESQL work but nothing production level.)
> More a MySQL shortcoming than embedded SQL.
> 
>> PostgreSQL - only C (from project itself - an open source Cobol exist)
> 
> And that's the way Open Source works.  If there was a need other
> languages would be supported.

It is not really open source specific.

If there is a demand for something then it will be created.
Maybe commercial. Maybe open source.

Given that MySQL/MariaDB is #2 in database market share
and PostgreSQL is #4 and they are used by by a huge number
of developers (magnitude 1 million), then the fact that there
are no pre-compilers for MySQL/MariaDB and only two for PostgreSQL
is a pretty good indication for very low interest for embedded
SQL among developers.

> All of this shows a lack of interest in languages that most people
> think are dying.  Also in database systems not being used for the
> kind of work that Oracle, RDP, DB2 and Postgres are.  I see nothing
> here that even hints at embedded SQL going away.

The fact that half the widely used databases has no pre-compilers
available and the remaining half only has support for typical
2-3 out of maybe 20 languages used for database access shows that
for the vast majority (95% magnitude) of projects then embedded
SQL is not possible because no pre-compiler exist.

And in the remaining few cases then it may be discarded due
to uncertainty about the future of the pre-compiler or because
the developers do not like it or don't know about it (most developers
under age 50 does not know that embedded SQL exist).

Cobol is probably the only language where embedded SQL will be
the most common choice for database access. The C/C++ crowd
has moved to various standards based or database specific API's.

Arne