|
1 | 1 |
|
2 | | -Readme for psqlodbc.dll 4/15/98 |
3 | | -------------------------------------------------------------------------------- |
4 | | -Latest binary and source updates available at http://www.insightdist.com/psqlodbc |
| 2 | +Readme for psqlodbc.dll 04/04/2001 |
| 3 | +----------------------------------------------------------------------------------- |
| 4 | +Precompiled binaries for Win32 are available from ftp://ftp.postgresql.org/pub/odbc |
5 | 5 |
|
6 | 6 |
|
7 | 7 | I. Building the Driver from the source code |
8 | 8 |
|
9 | 9 | This section describes how to build the PostgreSQL ODBC Driver (psqlodbc.dll). |
10 | | -Microsoft Visual C++ version 4.0 or higher is required. There is no manually |
11 | | -constructed Makefile. The visual C++ environment automatically generates one |
12 | | -during the build process. Thus, the project binary files (".ncb", ".mdp", ".aps") |
13 | | -nor the makefile are really distributed as part of the source code release |
14 | | -(although they are probably in there anyway). |
| 10 | +Microsoft Visual C++ version 4.0 or higher is required. Other compilers may work |
| 11 | +but have not been formally tested. The psqlodbc.dll may be built either in the |
| 12 | +VC++ IDE or from the command line: |
| 13 | + |
| 14 | +IDE Method |
| 15 | +---------- |
15 | 16 |
|
16 | 17 | 1. Create a new project workspace with the type DLL. For the name, type in the |
17 | 18 | name "psqlodbc". |
@@ -40,6 +41,17 @@ nor the makefile are really distributed as part of the source code release |
40 | 41 | 7. When complete, the "psqlodbc.dll" file is under the "Release" subdirectory. |
41 | 42 | (i.e., "\msdev\projects\psqlodbc\release\psqlodbc.dll") |
42 | 43 |
|
| 44 | +Command Line Method |
| 45 | +------------------- |
| 46 | + |
| 47 | +1. From a command prompt, CD to the directory containing the source code. |
| 48 | + |
| 49 | +2. Use NMAKE to build the dll eg: |
| 50 | + |
| 51 | + C:\psqlodbc\> nmake /f win32.mak CFG=Release ALL |
| 52 | + |
| 53 | + Possible configurations are Release, Debug, MultiByteRelease or MultiByteDebug |
| 54 | + Possible build types are ALL or CLEAN |
43 | 55 |
|
44 | 56 |
|
45 | 57 | II. Using Large Objects for handling LongVarBinary (OLE Objects in Access) |
@@ -70,26 +82,3 @@ But for now, it sure is fun to stick a Word document, Visio document, or avi of |
70 | 82 | baby into a database column, even if you will fill up your server's hard disk after a while! |
71 | 83 |
|
72 | 84 |
|
73 | | - |
74 | | -III. Using Row Versioning feature and creating the missing equals operator |
75 | | - |
76 | | -In order to use row versioning, you must overload the int4eq function for use |
77 | | -with the xid type. Also, you need to create an operator to compare xid to int4. |
78 | | -You must do this for each database you want to use this feature on. |
79 | | -Here are the details: |
80 | | - |
81 | | -create function int4eq(xid,int4) |
82 | | - returns bool |
83 | | - as '' |
84 | | - language 'internal'; |
85 | | - |
86 | | -create operator = ( |
87 | | - leftarg=xid, |
88 | | - rightarg=int4, |
89 | | - procedure=int4eq, |
90 | | - commutator='=', |
91 | | - negator='<>', |
92 | | - restrict=eqsel, |
93 | | - join=eqjoinsel |
94 | | - ); |
95 | | - |
0 commit comments