es
a decent job and can save you a lot of time. You still have to clean
some translations.
Look at the *.c & *.h \src\interfaces\libpq directory that comes with
the postgres source.
John
On 5/20/2012 7:51 AM, zeljko wrote:
John Townsend wrote:
It appears that some developers (Dav
In that case, yes, there are such implementations around. Martijn
mentioned a few, and I mentioned the Pike one, all of which do indeed
bypass libpq and talk directly to the server. It is, as I understand
it, an open and stable protocol, so it's no different from writing a
program that connects to
On 5/21/2012 7:56 AM, Merlin Moncure wrote:
On Sun, May 20, 2012 at 2:52 PM, John Townsend
wrote:
By by-passing the "dll" (or "so" on Linux) library I mean you write function
or procedure calls to the server that is running as a service on Windows.
You don't use
There are least 10 Procedural Languages
<http://en.wikipedia.org/wiki/PL/pgSQL> available for PostGreSQL. The
one that comes with the installation is PL/pgSQL.
Which ones do you use and why?
Thanks,
John Townsend
On 5/31/2012 3:13 PM, Mike Toews wrote:
On 1 June 2012 02:36, John Townsend wrote:
There are least 10 Procedural Languages available for PostGreSQL. The one
that comes with the installation is PL/pgSQL.
The count looks closer to 18
http://en.wikipedia.org/wiki/PostgreSQL#Procedural_languages
On 5/31/2012 10:52 PM, Chris Travers wrote:
Minor correction
On Thu, May 31, 2012 at 1:57 PM, John Townsend
wrote:
Fortran was the first computer language for me. (I guess that reveals my age
:-) )
Fortran was my second computer language, but I hated it.
PL/pgSQL is easy to learn for me
165 KB which was downloaded
(Enterprise site). I use C++ very little, so this is probably due to
compiler settings / flags, or perhaps just the use of just another compiler.
Thanks
John Townsend
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your
