From owner-freebsd-ports Tue Apr 23 06:22:32 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA01909 for ports-outgoing; Tue, 23 Apr 1996 06:22:32 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA01904 for ; Tue, 23 Apr 1996 06:22:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id GAA04914; Tue, 23 Apr 1996 06:22:04 -0700 (PDT) To: me@gw.muc.ditec.de cc: Trav757@aol.com, ports@freebsd.org Subject: Re: Programming API In-reply-to: Your message of "Tue, 23 Apr 1996 14:28:00 +0600." Date: Tue, 23 Apr 1996 06:22:04 -0700 Message-ID: <4912.830265724@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Providing a C API is still not the same as "embedded SQL", at least not as I've ever seen it defined in the commercial world. The Commercial SQL compilers I've worked with allow you to do direct variable and function referencing, with the SQL compiler handling all aspects of the rendevous behind your back. Jordan > In lists.freebsd.ports you write: > > >No, it is not. > > >> Is this msql product an embedded SQL product? I'm looking to write C/C++ a pps > >> which access databases using embedded SQL. > > I'd say it depends which way you look at it. Msql uses a server daemon > to handle the databases. There *IS* a C programming API to access msql > databases. In fact, the screen oriented msql client as well as the w3-msql > web frontend use it as that's the *only* way to stick data into a DB > or get it out. The client uses a TCP connection to the server to do its thing . > > Look at http://Hughes.com.au/ > > Michael > -- > Michael Elbel, DITEC, Muenchen, Germany - me@muc.ditec.de > Fermentation fault (coors dumped)