Date: Tue, 23 Apr 1996 15:43:31 +0200 (MSZ) From: me@tartufo.muc.ditec.de (Michael Elbel) To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: me@gw.muc.ditec.de, Trav757@aol.com, ports@freebsd.org Subject: Re: Programming API Message-ID: <m0uBiNP-000Pa6C@tartufo.muc.ditec.de> In-Reply-To: <4912.830265724@time.cdrom.com> from "Jordan K. Hubbard" at "Apr 23, 96 06:22:04 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. I've only done embedded SQL with Oracle and Ingres, so we may be talking about different things. Yes, you don't need a precompiler with msql, but that's optimization and convenience with other products. Compare the way msql does it with "dynamic sql" and you're pretty close. What you indeed can do is do something like: msqlQuery(sock, your_sql_statement); msqlStoreResult(); do any needed actions on the results. Sounds pretty much like what I've been used to with other dynamic esql stuff. I'd suggest having a look at the mSQL documentation :) Michael -- Michael Elbel, DITEC, Muenchen, Germany - me@muc.ditec.de Fermentation fault (coors dumped)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0uBiNP-000Pa6C>