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

[Arne Vajhøj]

On 10/12/2022 5:50 PM, Arne Vajhøj wrote:
> On 10/12/2022 5:45 PM, Jan-Erik Söderholm wrote:
>> Den 2022-10-12 kl. 23:43, skrev Arne Vajhøj:
>>> On 10/12/2022 5:33 PM, Arne Vajhøj wrote:
>>>> On 10/12/2022 4:20 PM, Bill Gunshannon wrote:
>>>>> Using a compatibility layer and trying to make PostGres look like
>>>>> RDB (or Oracle) would be a major mistake. Better to bite the bullet
>>>>> and move into the current century.
>>>>
>>>> It is a tradeoff.
>>>>
>>>> There are benefits from doing things the standard way instead of
>>>> doing it the compatibility way.
>>>>
>>>> But there are also huge cost of changing the client applications.
>>>>
>>>>>                                  I have never used RDB (I have
>>>>> used Oracle) but I assume it supports EXEC SQL and the usual SQL
>>>>> syntax.  If so, moving could be fairly easy.  If not, could be a
>>>>> problem.  Of course, probably also depends on the language being used.
>>>>
>>>> It will indeed depend on the language and the API used.
>>>>
>>>> embedded SQL/C => relative easy (PgSQL has precompiler)
>>>>
>>>> embedded SQL/Cobol => maybe easy (an open source precompiler 
>>>> supposedly exist and work)
>>>>
>>>> embedded SQL/Pascal, Fortran ... => major rewrite (precompilers are 
>>>> not available)
>>>
>>> Also note that moving to the current century implies
>>> moving from embedded SQL...
>>
>> To what?
> 
> ORM
> standard API (like ODBC, JDBC, DB API 2.0 etc.)
> database specific API (for PGSQL that means libpq*)
> 
> *) libpq is already ported to VMS - https://vmssoftware.com/products/libpq/

One obvious caveat: some languages are not well supported by these.

Arne