bug-apl
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-apl] ⎕SQL


From: Christian Robert
Subject: Re: [Bug-apl] ⎕SQL
Date: Fri, 6 Jan 2017 23:15:09 -0500
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0

I can help with MySQL/MariaDB

I have a C++ class made by myself more than 10 years ago (still compile fine in 
2017).

It may be a starting point. well we can discuss that. I can provide the source 
to help you if needed.

Yes Oracle interface is awful, I know. And it always near depend on version of 
the server.

About MS SQL, I don't know of any API available on Unix, able to connect to it. 
It's proprietary Microsoft API, I think
and really fine with me ;-)  As usual, I may be wrong.

Xtian.

On 2017-01-06 21:42, Elias Mårtenson wrote:
I personally have nothing against adding other providers, the API to do so is 
very simple and I'll be happy to help anyone who wants to do it.

It's just that I have neither interest nor need to do it myself, so I won't be 
the person doing this work.

I was looking into adding Oracle support, but the OCI library that you have to 
use to do that is absolutely awful, so I stopped that effort. I might pick it 
up again at some point if I really have the need to do that.

Regards,
Elias

On 7 Jan 2017 03:31, "Blake McBride" <address@hidden <mailto:address@hidden>> 
wrote:

    My component and keyed file systems are built on Elias' SQL DB interface.  
Do I need to convert those?

    Also, if we are making the SQL interface an integral part of GNU APL, I 
would really like to see MS SQL Server support added.

    Thanks!

    Blake


    On Fri, Jan 6, 2017 at 9:57 AM, Juergen Sauermann <address@hidden 
<mailto:address@hidden>> wrote:

        Hi,

        Elias (the author of the SQL native function) and myself have
        converted the previously native function into a system function named
        *⎕SQL*. Everything else remains the same.

        The *wslib5/SQL.apl* workspace was updated accordingly; if you use
        that workspace instead of the native function directly then you should
        not notice any differences.

        The native function for SQL will remain for a while, but disappear 
eventually.

        Enjoy,
        Jürgen







reply via email to

[Prev in Thread] Current Thread [Next in Thread]