Good job with the PostgreSQL ODBC driver Byron!

                      - Tom
Howdy all,

just a status update on MySQL problems.  According to one of our engineers
more familiar with Data, it would seem that I've been misinformed about
what levels of ODBC and SQL Grammar conformance we require:

    In my previous message I confused ODBC Conformance Levels with ODBC
    SQL Grammar Conformance Levels. We require Level 1 (beyond Core)
    ODBC Conformance, and we are still confused about SQL Grammer
    Conformance. It appears that we require "Extended SQL" grammar
    conformance, although we can probably code around this. There is an
    ODBC call to get the SQL Grammar conformance level from a driver.

I'm not certain yet what we'll do, but perhaps this can give folks an idea
of how MySQL could be changed to work better with Applix Data, even as we
investigate options for changing this from our side.  Perhaps PostgreSQL is
looking better.  :)

Eric

>>>>> Le.Hong.Boi@QUANTIC.AC.VN writes:

> Hi Applix guys,
> Thanks for your patch for libaxel.so. I have replaced new libaxel.so, 
> and the last error message does not appear.
> Now, there is another incompatible clause of MySQL. After editing the 
> records, when I call edit_commit@ method, another message box appears: 
-- 
Senior Software Engineer / ericding@applix.com               <><
Applix, Inc. / 112 Turnpike Road / Westboro MA 01581-2842

--
To unsubscribe from the list, send "unsubscribe applixware-list" in the
body of a message to majordomo@applix.com.  Before you ask a question,
check out the Applixware for Linux FAQ, Errata, and mailing list
archives at http://linux.applixware.com/ under "Applix Resources."
Fri, 22 Jan 1999 06:14:45 +0000
"Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
[Fwd: AWL: Re: Another unrecognized SQL clause in MySQL "WHERE
	CURRENT OF"]