Received: from golem.jpl.nasa.gov (root@hectic-3.jpl.nasa.gov
 [128.149.68.205])
	by hub.org (8.8.8/8.8.8) with ESMTP id KAA10419
	for <pgsql-interfaces@postgreSQL.org>;
	Sat, 3 Oct 1998 10:29:56 -0400 (EDT)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (localhost [127.0.0.1])
	by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id OAA20893;
	Sat, 3 Oct 1998 14:30:24 GMT
Sender: tgl@mythos.jpl.nasa.gov
Message-ID: <361634FE.68273D44@alumni.caltech.edu>
Date: Sat, 03 Oct 1998 14:30:22 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Organization: Caltech/JPL
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.30 i686)
MIME-Version: 1.0
To: Gerald Gryschuk <gerald.gryschuk@home.com>
CC: Byron Nikolaidis <byronn@insightdist.com>,
	pgsql-interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: Just some unfinished stuff.
References: <360C90C5.7A466671@home.com>
 <3614ED17.B0CA4B66@alumni.caltech.edu>
	<3615D4A1.B061C1C7@home.com>
Content-Type: multipart/mixed; boundary="------------1FDA1DE0AC8A6EFC5EEF5D5B"

This is a multi-part message in MIME format.
--------------1FDA1DE0AC8A6EFC5EEF5D5B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> > Speaking of docs, Byron, do you have a preference for how we will do
> > nice docs for the distribution? I've got some sgml source code for
> > Unix-side issues, but have not integrated any other information. 
> > Could you summarize what docs resources currently exist, and which 
> > ones you would like to see in the future?
> Oh goody. Real docs. I was hoping someone else would do them. Can I
> assume that if your writing "nice docs" that I don't have to write
> that new Readme I mentioned?

Well, I have good new and bad news...

First, the good news: We will have real odbc docs for this release.

Now the bad news: I'd like you to contribute to them *grin*

I've enclosed the existing sgml source and the html output (so you can
see what it looks like) for the odbc docs I've adapted and written.
afaik it doesn't have any of the generic or WIN32 info from Byron's
docs, but it should try to cover the Unix-specific stuff at least.

Could you look at it and add information you think is important? If you
get confused on the sgml markup just type in plain text in about the
right place without markup and I'll fix it up after you send it back
(maybe you can mark things with a "***" or "GGG" to make sure I find the
un-marked-up changes, if any).

At the moment I've got these docs in the Programmer's Guide, but I think
they should show up somewhere else, in either the User's Guide or the
Admin's Guide. Which would you vote for?

                      - Tom
--------------1FDA1DE0AC8A6EFC5EEF5D5B
Content-Type: text/html; charset=us-ascii; name="odbc.sgml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="odbc.sgml"
Content-Base: "file:/opt/postgres/current/doc/src/sgm
	l/odbc.sgml"

<Chapter Id="odbc">
<DocInfo>
<AuthorGroup>
<Author>
<FirstName>Tim</FirstName>
<Surname>Goeke</Surname>
</Author>
<Author>
<FirstName>Thomas</FirstName>
<Surname>Lockhart</Surname>
</Author>
</AuthorGroup>
<Date>1998-08-25</Date>
</DocInfo>

<Title>ODBC Interface</Title>

<Para>
<Note>
<Para>
Background information originally by
 <ULink url="mailto:tgoeke@xpressway.com">Tim Goeke</ULink>
</Para>
</Note>

<Para>
<acronym>ODBC</acronym> (Open Database Connectivity) is an abstract 
<acronym>API</acronym> 
which allows you to write standard "ODBC" applications.
<acronym>ODBC</acronym> provides a product-neutral interface 
between frontend applications and database servers,
allowing a user or developer to write applications which are portable among servers.

<Sect1>
<Title>Background</Title>

<Para>
The <acronym>ODBC</acronym> <acronym>API</acronym> matches up 
on the backend to an <acronym>ODBC</acronym>-compatible data source.
This could be anything from a text file to an Oracle or 
<productname>Postgres</productname> <acronym>RDBMS</acronym>.

<Para>
The backend access come from <acronym>ODBC</acronym> drivers, or vendor specifc drivers that
allow data access.   <productname>psqlODBC</productname> is such a driver, along with others that are
available, such as the OpenLink <acronym>ODBC</acronym> drivers.

<Para>
Once you write an <acronym>ODBC</acronym> application, you SHOULD be able to connect to ANY
back end database, regardless of the vendor, as long as the database schema
is the same.

<Para>
For example. you could have <productname>MS SQL Server</productname>
 and <productname>Postgres</productname> servers which have
exactly the same data.  Using <acronym>ODBC</acronym>, your Windows app would make exactly the
same calls and the back end data source would look the same (to the windows
app).

<para>
<ulink url="http://www.insightdist.com/">Insight Distributors</ulink> provides active and ongoing
support for the core <productname>psqlODBC</productname> distribution. They provide a
<ulink url="http://www.insightdist.com/psqlodbc/"><acronym>FAQ</acronym></ulink>, ongoing development
on the code base, and actively participate on the 
<ulink url="mailto:interfaces@postgresql.org">interfaces mailing list</ulink>.

<sect1>
<title><productname>Windows</productname> Applications</title>

<Para>
In the real world, differences in drivers and the level of <acronym>ODBC</acronym> support
lessens the potential of <acronym>ODBC</acronym>:

<SimpleList>
<Member>
Access, Delphi, and Visual Basic all support <acronym>ODBC</acronym> directly.

<Member>
Under C++, such as Visual C++, you can use the C++ <acronym>ODBC</acronym> <acronym>API</acronym>.

<Member>
In Visual C++, you can use the CRecordSet class, which wraps the 
<acronym>ODBC</acronym> <acronym>API</acronym>
set within an MFC 4.2 class.  This is the easiest route if you are doing
Windows C++ development under Windows NT.
</SimpleList>

<Para>
If I write an app for <productname>Postgres</productname> 
can I write it using <acronym>ODBC</acronym> calls
to the <productname>Postgres</productname> server, or is that only when another database program 
like MS SQL Server or Access needs to access the data?

<Para>
Again, the <acronym>ODBC</acronym> <acronym>API</acronym> set is the way to go.
You can find out more at
Microsoft's web site or in your Visual C++ docs (if that's what you are using.)

<Para>
Visual Basic and the other RAD tools have Recordset objects that use <acronym>ODBC</acronym>
directly to access data.  Using the data-aware controls, you can quickly
link to the <acronym>ODBC</acronym> back end database (<Emphasis>very</Emphasis> quickly).

<Para>
Playing around with MS Access will help you sort this out.  Try using
File->Get External Data

<Para>
<Tip>
<Para>
You'll have to set up a DSN first.
</Para>
</Tip>

<!--
<Para>
<Tip>
<Para>
The <productname>Postgres</productname> datetime type will break MS Access.
</Para>
</Tip>
-->

<sect1>
<title>Unix Applications</title>

<para>
<productname>ApplixWare</productname> has an <acronym>ODBC</acronym> database interface
supported on at least some platforms. <productname>ApplixWare</productname> v4.4.1 has been
demonstrated under Linux with <productname>Postgres</productname> v6.4 
using the <productname>psqlODBC</productname>
driver contained in the <productname>Postgres</productname> distribution.

<sect2>
<title>Configuration Files</title>

<para>
The <filename>~/.odbc.ini</filename> contains user-specified access information 
for the <productname>psqlODBC</productname>
driver. The file uses conventions typical for <productname>Windows</productname> 
Registry files, but despite this
restriction can be made to work.

<para>
Here is an example <filename>.odbc.ini</filename> file, 
showing access information for three databases:

<programlisting>
[ODBC Data Sources]
DataEntry = Read/Write Database
QueryOnly = Read-only Database
Test = Debugging Database
Default = Postgres Stripped

[DataEntry]
ReadOnly = 0
Servername = localhost
Database = Sales

[QueryOnly]
ReadOnly = 1
Servername = localhost
Database = Sales

[Test]
Debug = 1
CommLog = 1
ReadOnly = 0
Servername = localhost
Username = tgl
Password = "no$way"
Port = 5432
Database = test

[Default]
Servername = localhost
Database = tgl
Driver = /opt/postgres/current/lib/libpsqlodbc.so

[ODBC]
InstallDir = /opt/applix/axdata/axshlib
</programlisting>

<para>
For Applix, here is an example ~/axhome/macros/login.am file:
<programlisting>
macro login
        set_set_system_var@("sql_username@","tgl")
        set_system_var@("sql_passwd@","no$way")
endmacro
</programlisting>

<sect1>
<title>Supported Platforms</title>

<para>
<productname>psqlODBC</productname> has been built and tested 
on <productname>Linux</productname>. There have been reports of success 
with FreeBSD and with Solaris.

</Chapter>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"../reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:"/usr/lib/sgml/catalog"
sgml-local-ecat-files:nil
End:
-->

--------------1FDA1DE0AC8A6EFC5EEF5D5B
Content-Type: text/html; charset=us-ascii; name="odbc.htm"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="odbc.htm"
Content-Base: "file:/opt/postgres/current/doc/src/sgm
	l/odbc.htm"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>ODBC Interface</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet version 1.18"><LINK
REL="HOME"
TITLE="PostgreSQL Programmer's Guide"
HREF="programmer.htm"><LINK
REL="PREVIOUS"
TITLE="pg_lo_export"
HREF="pgtcl-pgloexport.htm"><LINK
REL="NEXT"
TITLE="Windows Applications"
HREF="odbc4084.htm"></HEAD
><BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PostgreSQL Programmer's Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="pgtcl-pgloexport.htm"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="odbc4084.htm"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="ODBC"
>Chapter 19. ODBC Interface</A
></H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
><A
HREF="odbc.htm#AEN4060"
>Background</A
></DT
><DT
><A
HREF="odbc4084.htm"
><SPAN
CLASS="PRODUCTNAME"
>Windows</SPAN
> Applications</A
></DT
><DT
><A
HREF="odbc4114.htm"
>Unix Applications</A
></DT
><DT
><A
HREF="odbc4134.htm"
>Supported Platforms</A
></DT
></DL
></DIV
><P
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>Background information originally by
 <A
HREF="mailto:tgoeke@xpressway.com"
TARGET="_top"
>Tim Goeke</A
></P
></BLOCKQUOTE
>&#13;</P
><P
><SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> (Open Database Connectivity) is an abstract 
<SPAN
CLASS="ACRONYM"
>API</SPAN
> 
which allows you to write standard "ODBC" applications.
<SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> provides a product-neutral interface 
between frontend applications and database servers,
allowing a user or developer to write applications which are portable among servers.&#13;</P
><H1
CLASS="SECT1"
><A
NAME="AEN4060"
>Background</A
></H1
><P
>The <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> <SPAN
CLASS="ACRONYM"
>API</SPAN
> matches up 
on the backend to an <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
>-compatible data source.
This could be anything from a text file to an Oracle or 
<SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> <SPAN
CLASS="ACRONYM"
>RDBMS</SPAN
>.&#13;</P
><P
>The backend access come from <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> drivers, or vendor specifc drivers that
allow data access.   <SPAN
CLASS="PRODUCTNAME"
>psqlODBC</SPAN
> is such a driver, along with others that are
available, such as the OpenLink <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> drivers.&#13;</P
><P
>Once you write an <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> application, you SHOULD be able to connect to ANY
back end database, regardless of the vendor, as long as the database schema
is the same.&#13;</P
><P
>For example. you could have <SPAN
CLASS="PRODUCTNAME"
>MS SQL Server</SPAN
>
 and <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> servers which have
exactly the same data.  Using <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
>, your Windows app would make exactly the
same calls and the back end data source would look the same (to the windows
app).&#13;</P
><P
><A
HREF="http://www.insightdist.com/"
TARGET="_top"
>Insight Distributors</A
> provides active and ongoing
support for the core <SPAN
CLASS="PRODUCTNAME"
>psqlODBC</SPAN
> distribution. They provide a
<A
HREF="http://www.insightdist.com/psqlodbc/"
TARGET="_top"
><SPAN
CLASS="ACRONYM"
>FAQ</SPAN
></A
>, ongoing development
on the code base, and actively participate on the 
<A
HREF="mailto:interfaces@postgresql.org"
TARGET="_top"
>interfaces mailing list</A
>.&#13;</P
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="pgtcl-pgloexport.htm"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="programmer.htm"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="odbc4084.htm"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>pg_lo_export</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><SPAN
CLASS="PRODUCTNAME"
>Windows</SPAN
> Applications</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--------------1FDA1DE0AC8A6EFC5EEF5D5B
Content-Type: text/html; charset=us-ascii; name="odbc4084.htm"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="odbc4084.htm"
Content-Base: "file:/opt/postgres/current/doc/src/sgm
	l/odbc4084.htm"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Windows Applications</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet version 1.18"><LINK
REL="HOME"
TITLE="PostgreSQL Programmer's Guide"
HREF="programmer.htm"><LINK
REL="UP"
TITLE="ODBC Interface"
HREF="odbc.htm"><LINK
REL="PREVIOUS"
TITLE="ODBC Interface"
HREF="odbc.htm"><LINK
REL="NEXT"
TITLE="Unix Applications"
HREF="odbc4114.htm"></HEAD
><BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PostgreSQL Programmer's Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="odbc.htm"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 19. ODBC Interface</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="odbc4114.htm"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
CLASS="SECT1"
><A
NAME="AEN4084"
><SPAN
CLASS="PRODUCTNAME"
>Windows</SPAN
> Applications</A
></H1
><P
>In the real world, differences in drivers and the level of <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> support
lessens the potential of <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
>:

<P
></P
><TABLE
BORDER="0"
><TR
><TD
>Access, Delphi, and Visual Basic all support <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> directly.&#13;</TD
></TR
><TR
><TD
>Under C++, such as Visual C++, you can use the C++ <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> <SPAN
CLASS="ACRONYM"
>API</SPAN
>.&#13;</TD
></TR
><TR
><TD
>In Visual C++, you can use the CRecordSet class, which wraps the 
<SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> <SPAN
CLASS="ACRONYM"
>API</SPAN
>
set within an MFC 4.2 class.  This is the easiest route if you are doing
Windows C++ development under Windows NT.</TD
></TR
></TABLE
><P
></P
>&#13;</P
><P
>If I write an app for <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> 
can I write it using <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> calls
to the <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> server, or is that only when another database program 
like MS SQL Server or Access needs to access the data?&#13;</P
><P
>Again, the <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> <SPAN
CLASS="ACRONYM"
>API</SPAN
> set is the way to go.
You can find out more at
Microsoft's web site or in your Visual C++ docs (if that's what you are using.)&#13;</P
><P
>Visual Basic and the other RAD tools have Recordset objects that use <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
>
directly to access data.  Using the data-aware controls, you can quickly
link to the <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> back end database (<I
CLASS="EMPHASIS"
>very</I
> quickly).&#13;</P
><P
>Playing around with MS Access will help you sort this out.  Try using
File-&#62;Get External Data&#13;</P
><P
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
>You'll have to set up a DSN first.</P
></BLOCKQUOTE
>
&#13;</P
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="odbc.htm"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="programmer.htm"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="odbc4114.htm"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>ODBC Interface</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="odbc.htm"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Unix Applications</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--------------1FDA1DE0AC8A6EFC5EEF5D5B
Content-Type: text/html; charset=us-ascii; name="odbc4114.htm"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="odbc4114.htm"
Content-Base: "file:/opt/postgres/current/doc/src/sgm
	l/odbc4114.htm"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Unix Applications</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet version 1.18"><LINK
REL="HOME"
TITLE="PostgreSQL Programmer's Guide"
HREF="programmer.htm"><LINK
REL="UP"
TITLE="ODBC Interface"
HREF="odbc.htm"><LINK
REL="PREVIOUS"
TITLE="Windows Applications"
HREF="odbc4084.htm"><LINK
REL="NEXT"
TITLE="Supported Platforms"
HREF="odbc4134.htm"></HEAD
><BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PostgreSQL Programmer's Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="odbc4084.htm"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 19. ODBC Interface</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="odbc4134.htm"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
CLASS="SECT1"
><A
NAME="AEN4114"
>Unix Applications</A
></H1
><P
><SPAN
CLASS="PRODUCTNAME"
>ApplixWare</SPAN
> has an <SPAN
CLASS="ACRONYM"
>ODBC</SPAN
> database interface
supported on at least some platforms. <SPAN
CLASS="PRODUCTNAME"
>ApplixWare</SPAN
> v4.4.1 has been
demonstrated under Linux with <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> v6.4 
using the <SPAN
CLASS="PRODUCTNAME"
>psqlODBC</SPAN
>
driver contained in the <SPAN
CLASS="PRODUCTNAME"
>Postgres</SPAN
> distribution.&#13;</P
><H2
CLASS="SECT2"
><A
NAME="AEN4123"
>Configuration Files</A
></H2
><P
>The <TT
CLASS="FILENAME"
>~/.odbc.ini</TT
> contains user-specified access information 
for the <SPAN
CLASS="PRODUCTNAME"
>psqlODBC</SPAN
>
driver. The file uses conventions typical for <SPAN
CLASS="PRODUCTNAME"
>Windows</SPAN
> 
Registry files, but despite this
restriction can be made to work.&#13;</P
><P
>Here is an example <TT
CLASS="FILENAME"
>.odbc.ini</TT
> file, 
showing access information for three databases:

<PRE
CLASS="PROGRAMLISTING"
>[ODBC Data Sources]
DataEntry = Read/Write Database
QueryOnly = Read-only Database
Test = Debugging Database
Default = Postgres Stripped

[DataEntry]
ReadOnly = 0
Servername = localhost
Database = Sales

[QueryOnly]
ReadOnly = 1
Servername = localhost
Database = Sales

[Test]
Debug = 1
CommLog = 1
ReadOnly = 0
Servername = localhost
Username = tgl
Password = "no$way"
Port = 5432
Database = test

[Default]
Servername = localhost
Database = tgl
Driver = /opt/postgres/current/lib/libpsqlodbc.so

[ODBC]
InstallDir = /opt/applix/axdata/axshlib</PRE
>&#13;</P
><P
>For Applix, here is an example ~/axhome/macros/login.am file:
<PRE
CLASS="PROGRAMLISTING"
>macro login
        set_set_system_var@("sql_username@","tgl")
        set_system_var@("sql_passwd@","no$way")
endmacro</PRE
>&#13;</P
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="odbc4084.htm"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="programmer.htm"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="odbc4134.htm"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><SPAN
CLASS="PRODUCTNAME"
>Windows</SPAN
> Applications</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="odbc.htm"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Supported Platforms</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--------------1FDA1DE0AC8A6EFC5EEF5D5B
Content-Type: text/html; charset=us-ascii; name="odbc4134.htm"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="odbc4134.htm"
Content-Base: "file:/opt/postgres/current/doc/src/sgm
	l/odbc4134.htm"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Supported Platforms</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet version 1.18"><LINK
REL="HOME"
TITLE="PostgreSQL Programmer's Guide"
HREF="programmer.htm"><LINK
REL="UP"
TITLE="ODBC Interface"
HREF="odbc.htm"><LINK
REL="PREVIOUS"
TITLE="Unix Applications"
HREF="odbc4114.htm"><LINK
REL="NEXT"
TITLE="JDBC Interface"
HREF="jdbc.htm"></HEAD
><BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PostgreSQL Programmer's Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="odbc4114.htm"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 19. ODBC Interface</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="jdbc.htm"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
CLASS="SECT1"
><A
NAME="AEN4134"
>Supported Platforms</A
></H1
><P
><SPAN
CLASS="PRODUCTNAME"
>psqlODBC</SPAN
> has been built and tested 
on <SPAN
CLASS="PRODUCTNAME"
>Linux</SPAN
>. There have been reports of success 
with FreeBSD and with Solaris.&#13;</P
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="odbc4114.htm"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="programmer.htm"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="jdbc.htm"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Unix Applications</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="odbc.htm"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>JDBC Interface</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
--------------1FDA1DE0AC8A6EFC5EEF5D5B--