|
1 | | -<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> |
2 | | -<html><head><title>PgAccess - a Tcl/Tk interface for PostgreSQL</title></head> |
3 | | -<bodybgcolor="#C0C0C0"> |
4 | | -<h1>PgAccess - a Tcl/Tk interface for PostgreSQL</h1> |
5 | | -<hr> |
6 | | -<aname="intro"> |
7 | | -<ul><li><ahref="intro.html">Introduction</a> |
8 | | -<ul><li><ahref="intro.html#whatpga">What is PgAccess?</a> |
9 | | -<li><ahref="intro.html#helppga">How to get help with PgAccess</a> |
10 | | -</ul> |
11 | | -<aname="start"> |
12 | | -<li><ahref="start.html">Getting Started</a> |
13 | | -<ul><li><ahref="start.html#getpga">How to get PgAccess</a> |
14 | | -<li><ahref="start.html#uncpga">How to uncompress PgAccess</a> |
15 | | -<li><ahref="start.html#putpga">Putting PgAccess where it will be found</a> |
16 | | -<li><ahref="start.html#startpga">Starting PgAccess</a> |
17 | | -<li><ahref="irix.html">Installing PgAccess under IRIX 5.3</a> |
18 | | -</ul> |
19 | | -<aname="problems"> |
20 | | -<li><ahref="problems.html">Common Problems with PgAccess</a> |
21 | | -<ul><li><ahref="problems.html#connfail">Connection failure</a> |
22 | | -<li><ahref="problems.html#libpg">libpgtcl not found</a> |
23 | | -<li><ahref="problems.html#spchar">Locale specific characters</a> |
24 | | -<li><ahref="problems.html#pg63">Problems with PostgreSQL 6.3.x</a> |
25 | | -</ul> |
26 | | -</ul> |
27 | | -</body></html> |
28 | | -<html><head><title>PgAccess - Introduction</title></head> |
29 | | -<bodybgcolor="#C0C0C0"> |
30 | | -<h1>PgAccess - Introduction</h1> |
31 | | -<aname="whatpga"><h2>What is PgAccess?</h2> |
32 | | -PgAccess is a graphical user interface for the PostgreSQL database management |
33 | | -system written in the Tcl/Tk scripting language by Constantin Teodorescu. It |
34 | | -allows the user to interact with PostgreSQL in a manner similar to many PC |
35 | | -database applications, with menu choices and graphical tools like buttons. |
36 | | -This means that the user can avoid the basic command line interface for most |
37 | | -common tasks. PgAccess doesn't change the way PostgreSQL operates, just makes |
38 | | -it easier to use for those familiar with graphical interfaces.<p> |
39 | | -Obviously, you<u>must</u> have PostgreSQL installed and running, and Tcl/Tk on |
40 | | -your system before you can use PgAccess.<p> |
41 | | -PgAccess is an "open source" application. The source code is available to the |
42 | | -user, and may be modified by the user. The user can fix a bug, or change the |
43 | | -way a function operates. You may not want to get that involved with the |
44 | | -programming, but you have the option to do so. If you feel you have made an |
45 | | -improvement to the program, you are encouraged to share it with other users.<p> |
46 | | -If you are not familiar with how open source software can be altered and |
47 | | -redistributed, please read<ahref="copyright.html">this</a>.<p> |
48 | | -<aname="helppga"><h2>How to get help with PgAccess</h2> |
49 | | -The mailing list for PgAccess is:<b>pgsql-interfaces@postgresql.org</b><p> |
50 | | -If you have any questions regarding PgAccess you should subscribe to this |
51 | | -list in the following way:<p> |
52 | | -First subscribe to the list by sending an email message to:<p> |
53 | | -<samp>pgsql-interfaces-request@postgresql.org</samp><p> |
54 | | -Send a single line in the body of the message as follows:<p> |
55 | | -<samp>subscribe</samp><p> |
56 | | -In a short time you should receive a message beginning like this:<p> |
57 | | -<samp>Welcome to the pgsql-interfaces mailing list!<br> |
58 | | -...</samp><p> |
59 | | -This will contain instructions on how to remove yourself from the mailing |
60 | | -list, so save that message. You may only want to ask a few questions and then |
61 | | -stop receiving messages.<p> |
62 | | -You may also email<ahref="mailto:teo@flex.ro">Constantin Teodorescu</a> |
63 | | -directly, although writing to a mailing list with many correspondents will often |
64 | | -produce a quicker answer.<p> |
65 | | -<ahref="index.html#intro">Back to index</a> |
66 | | -</body></html> |
67 | | -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
68 | 1 | <HTML> |
69 | 2 | <HEAD> |
70 | | -<TITLE>PgAccess on Irix</TITLE> |
71 | | -<METANAME="GENERATOR"CONTENT="Mozilla/3.04Gold (X11; I; Linux 2.0.33 i586) [Netscape]"> |
| 3 | +<METAHTTP-EQUIV="Content-Type"CONTENT="text/html; charset=iso-8859-1"> |
| 4 | +<METANAME="GENERATOR"CONTENT="Mozilla/4.03 [en] (X11; I; Linux 2.0.30 i586) [Netscape]"> |
| 5 | +<TITLE>PgAccess - Copyright notice</TITLE> |
72 | 6 | </HEAD> |
73 | | -<BODYTEXT="#000000"BGCOLOR="#FFFFFF"LINK="#0000EF"VLINK="#51188E"ALINK="#FF0000"> |
74 | | - |
75 | | -<H1>INSTALLING PgAccess UNDER IRIX 5.3. |
76 | | -<HRWIDTH="100%"></H1> |
77 | | - |
78 | | -<P><B><FONTCOLOR="#000080">This HOWO-TO make PgAccess working under Irix |
79 | | -is written by Stuart Rison</FONT></B></P> |
80 | | - |
81 | | -<P>These are the steps that I had to follow to get pgaccess to run on an |
82 | | -INDIGO2 running postgreSQL 6.3.2 under IRIX 5.3. I make no guarantee whatsoever |
83 | | -that the same step will work for others but at least it should point you |
84 | | -in the right direction. Also, I am a biologist by training so I only got |
85 | | -pgaccess working by fudging (that is, trial and error) this means that |
86 | | -some of the steps may be unnecessary (e.g. compiling $postgreSQL_source/src/interfaces/libpgtcl |
87 | | -as both a shared and static library) and they certainly haven't been optimised |
88 | | -(I know nothing about compiler switches etc.).</P> |
89 | | - |
90 | | -<P><B>1) Requirements:</B></P> |
91 | | - |
92 | | -<UL> |
93 | | -<P>You will need:</P> |
94 | | - |
95 | | -<UL> |
96 | | -<LI>postgreSQL source (http://www.postgresql.org)</LI> |
97 | | - |
98 | | -<LI>tcl8.0 source (http://www.tclconsortium.org/)</LI> |
99 | | - |
100 | | -<LI>tk8.0 source (http://www.tclconsortium.org/)</LI> |
101 | | - |
102 | | -<LI>pgaccess source (http://www.flex.ro/pgaccess)</LI> |
103 | | -</UL> |
104 | | -</UL> |
105 | | - |
106 | | -<P><B>2) Installation:</B></P> |
107 | | - |
108 | | -<P>a) tcl/tk:</P> |
109 | | - |
110 | | -<UL> |
111 | | -<P>You must first install tcl and then tk (in that order). I just used |
112 | | -./configure, no switches and gmake. Their installation should be trouble |
113 | | -free. Then you must move headers and libraries to the right places so:</P> |
114 | | - |
115 | | -<P>Header files: both tcl and tk have a header file (tcl.h and tk.h). The |
116 | | -tcl.h file is in $tcl_source_dir/generic and the tk.h file is in $tk_source_dir/generic; |
117 | | -both should be copied to /usr/local/include.</P> |
118 | | - |
119 | | -<P>Libraries: compilation (with cc) of tcl and tk yield libraries libtcl8.0.a |
120 | | -and libtk8.0.a in $source_dir/unix. Both should be copied to /usr/local/lib.</P> |
121 | | -</UL> |
122 | | - |
123 | | -<P>b) postgreSQL:</P> |
124 | | - |
125 | | -<UL> |
126 | | -<P>Make sure you have a fully patched postgreSQL source. If your ./configure |
127 | | -says it can't load 'IRIX' settings then you most probably will need to |
128 | | -patch ./configure.</P> |
129 | | - |
130 | | -<P>Configure using ./configure with the following switches: ./configure |
131 | | ---with-includes=/usr/local/include</P> |
132 | | - |
133 | | -<P>--with-libraries=/usr/local/lib --with-tcl [this and previous line as |
134 | | -one]</P> |
135 | | - |
136 | | -<P>Then make, make install as usual</P> |
137 | | -</UL> |
138 | | - |
139 | | -<P>c) Compiling libpgtcl:</P> |
140 | | - |
141 | | -<UL> |
142 | | -<P>The source for libpgtcl is in $postgreSQL_directory/src/interfaces/libpgsql.</P> |
143 | | - |
144 | | -<P>I do this twice. Once with just gmake. This produces a static library |
145 | | -libpgtcl.a which I leave where it is (I don't know what to do with it but |
146 | | -it may just come in handy). The I modify Makefile manually with a text |
147 | | -editor. Essentially I modify two line:</P> |
148 | | - |
149 | | -<P>before:</P> |
150 | | - |
151 | | -<P># Shared library stuff</P> |
152 | | - |
153 | | -<P>install-shlib-dep := shlib :=</P> |
154 | | - |
155 | | -<P>after:</P> |
156 | | - |
157 | | -<P># Shared library stuff</P> |
158 | | - |
159 | | -<P>install-shlib-dep := install-shlib shlib := libpgtcl.so.1</P> |
160 | | - |
161 | | -<P>Then gmake -f Makefile_modified. This creates two shared (.so) libraries: |
162 | | -libpgtcl.so and libpgtcl.so.1. I can't tell the difference between them |
163 | | -so I copied them both to /usr/lib/.</P> |
164 | | -</UL> |
165 | | - |
166 | | -<P>d) running pgaccess:</P> |
167 | | - |
168 | | -<UL> |
169 | | -<P>Uncompress pgaccess (usually with gunzip and tar). So long as 'wish' |
170 | | -(a binary produced when compiling tk8.0) is somewhere in your path, you |
171 | | -should be able to run pgaccess with:</P> |
172 | | - |
173 | | -<P>wish -f $pgaccess_dir/pgaccess.tcl [postgreSQL_database_name]</P> |
174 | | -</UL> |
175 | | - |
176 | | -<P>e) et voila!</P> |
177 | | - |
178 | | -<P><B>3) Concluding remarks:</B></P> |
179 | | - |
180 | | -<UL> |
181 | | -<P>As I stated at the start of this document, following the procedure indicated |
182 | | -above worked for me. I am sure, however, that a few of the steps are unnecessary/non-optimised/stupid |
183 | | -etc. If any Unix (IRIX) boffin is reading this and you spot anything you |
184 | | -would like to comment/correct etc. please e-mail me (stuart@ludwig.ucl.ac.uk). |
185 | | -Also, if you just have questions and think I might help, please contact |
186 | | -me at the same e-mail.</P> |
187 | | - |
188 | | -<P>Finally, I can accept no responsibility if these steps don't work for |
189 | | -you or if it all goes horribly wrong and you 'damage' your computer trying |
190 | | -them. Let common sense prevail!</P> |
191 | | -</UL> |
192 | | - |
193 | | -<P>Good luck</P> |
194 | | - |
195 | | -<P>Stuart Rison LICR University College London London W1P 8BT<BR> |
196 | | -<AHREF="mailto:stuart@ludwig.ucl.ac.uk">stuart@ludwig.ucl.ac.uk</A></P> |
197 | | -<ahref="index.html#start">Back to index</a> |
| 7 | +<BODYBGCOLOR="#FFFFFF"> |
| 8 | +<TT>---------------------------------------------------------------------------</TT> |
| 9 | +<BR><TT></TT> |
| 10 | +<BR><TT></TT> <TT></TT> |
| 11 | + |
| 12 | +<P><TT>Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group</TT> |
| 13 | +<P><TT>Portions Copyright (c) 1994, Regents of the University of California</TT> |
| 14 | + |
| 15 | +<P><TT>Permission to use, copy, modify, and distribute this software and |
| 16 | +its</TT> |
| 17 | +<BR><TT>documentation for any purpose, without fee, and without a written |
| 18 | +agreement</TT> |
| 19 | +<BR><TT>is hereby granted, provided that the above copyright notice and |
| 20 | +this</TT> |
| 21 | +<BR><TT>paragraph and the following two paragraphs appear in all copies.</TT><TT></TT> |
| 22 | + |
| 23 | +<P><TT>IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY |
| 24 | +PARTY FOR</TT> |
| 25 | +<BR><TT>DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, |
| 26 | +INCLUDING</TT> |
| 27 | +<BR><TT>LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS</TT> |
| 28 | +<BR><TT>DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED |
| 29 | +OF THE</TT> |
| 30 | +<BR><TT>POSSIBILITY OF SUCH DAMAGE.</TT><TT></TT> |
| 31 | + |
| 32 | +<P><TT>THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,</TT> |
| 33 | +<BR><TT>INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY</TT> |
| 34 | +<BR><TT>AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER |
| 35 | +IS</TT> |
| 36 | +<BR><TT>ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS |
| 37 | +TO</TT> |
| 38 | +<BR><TT>PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.</TT> |
198 | 39 | </BODY> |
199 | 40 | </HTML> |
200 | | -<html><head><title>PgAccess - Common Problems</title></head> |
201 | | -<bodybgcolor="#C0C0C0"> |
202 | | -<h1>Common Problems with PgAccess</h1> |
203 | | -<aname="connfail"><h2>Connection failure</h2> |
204 | | -One of the most common initial problems is the message:<p> |
205 | | -<samp>Error connecting database<br> |
206 | | -Connection to database failed<br> |
207 | | -connectDB() failed: Is the<br> |
208 | | -postmaster running and<br> |
209 | | -accepting TCP/IP (with -i)<br> |
210 | | -connections at 'localhost' on<br> |
211 | | -port '5432'?</samp><p> |
212 | | -This usually occurs because the "postmaster" (the postgreSQL backend) was not |
213 | | -started with the<samp>-i</samp> option. Usually just adding<samp>-i</samp> to |
214 | | -the command line that starts the postmaster and restarting will fix this. |
215 | | -<aname="libpg"><h2>libpgtcl not found</h2> |
216 | | -PgAccess requires a library of functions named<samp>libpgtcl</samp>. This |
217 | | -should be available with the postgreSQL distribution, and is usually placed in |
218 | | -the correct location when installing postgreSQL. First check that there is a |
219 | | -file named<samp>libpgtcl.so</samp> (perhaps with a number appended - or |
220 | | -<samp>libpgtcl.dll</samp> on Windows systems) on your |
221 | | -system. If not, you will have to download and perhaps compile this library.<p> |
222 | | -<samp>ftp://ftp.flex.ro/pub/pgaccess</samp><p> |
223 | | -is one place that you can download precompiled libpgtcl libraries for |
224 | | -PgAccess.<p> |
225 | | -<aname="spchar"> |
226 | | -<h2>Locale specific characters</h2> |
227 | | -This problem occurs with some special characters used in different |
228 | | -countries because PgAccess did not use fonts with `-ISO8859-1' encoding.<p> |
229 | | -One solution was proposed by H.P.Heidinger ( hph@hphbbs.ruhr.de) and |
230 | | -is very simple.<p> |
231 | | -If you look in the file pgaccess.tcl, you will find the fonts declared in |
232 | | -this manner:<p> |
233 | | -<TT>$ grep -e '-font' -i pgaccess.tcl<BR> |
234 | | --font -Adobe-Helvetica-Medium-R-Normal--*-120-*-*-*-*-*-* \<br> |
235 | | -...</TT></P> |
236 | | -The font declarations should be altered to:<p> |
237 | | -<tt>-font -Adobe-Helvetica-Medium-R-Normal-*-*-120-*-*-*-*-iso8859-1<br> |
238 | | -...</tt><p> |
239 | | -That is, inserting an asterisk between the first pair of hyphens, and changing |
240 | | -the final two asterisks to<samp>iso8859</samp> and<samp>1</samp> |
241 | | -respectively.<p> |
242 | | -You can alter the source code by running the following script : |
243 | | -<P><TT>#!/bin/sh<BR> |
244 | | -cp pgaccess.tcl pgaccess.tcl-org<BR> |
245 | | -cat pgaccess.tcl |\<BR> |
246 | | -sed -e's/\-\*\-\*\ /\-iso8859\-1\ /g' |\<BR> |
247 | | -sed -e's/\-\*\-\*\}/\-iso8859\-1}/g' |\<BR> |
248 | | -sed -e's/\-\*\-\*\]/\-iso8859\-1]/g' |\<BR> |
249 | | -sed -e's/\-\*\-\*$/\-iso8859\-1/g' |\<BR> |
250 | | -sed -e's/\-Clean\-/\-Fixed\-/g' |\<BR> |
251 | | -sed -e's/clean/fixed/g' >pgaccess.iso<BR> |
252 | | -mv pgaccess.iso pgaccess.tcl<BR> |
253 | | -chmod +x pgaccess.tcl</TT><P> |
254 | | -The final version of PgAccess (1.0) will let the user decide what fonts |
255 | | -will be used through a "preferences" dialog window.</p> |
256 | | -<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> |
257 | | -a name="pg63"> |
258 | | -<h2>Problem with PostgreSQL 6.3.x</h2> |
259 | | -PgAccess 0.93 and later may have problems working with PostgreSQL 6.3.x. |
260 | | -Changes in libpgtcl have been made to remove these, but if you are |
261 | | -using PostgreSQL 6.3.x, this patch will allow you to get around the problems.<p> |
262 | | -In the procedure<tt>wpg_exec</tt> change the following line:<p> |
263 | | -<tt>set pgsql(errmsg) [pg_result $pgsql(res) -error]</tt><p> |
264 | | -to this:<p> |
265 | | -<tt>set pgsql(errmsg) "NO ERROR INFORMATION SUPPLIED"</tt><p> |
266 | | -and the program will work. The only disadvantage is that with some error |
267 | | -conditions, you will not get the appropriate error message from libpgtcl.<p> |
268 | | -<ahref="index.html#problems">Back to index</a> |
269 | | -</body></html> |
270 | | -<html><head><title>PgAccess - Getting Started</title></head> |
271 | | -<bodybgcolor="#C0C0C0"> |
272 | | -<h1>PgAccess - Getting Started</h1> |
273 | | -<aname="getpga"><h2>How to get PgAccess</h2> |
274 | | -If you have this HTML help system, you have probably already downloaded |
275 | | -PgAccess. If not, or you wish to download the latest version, it is available |
276 | | -from the URL:<p> |
277 | | -<samp>http://www.flex.ro</samp><p> |
278 | | -The home page will contain instructions on which files to download for your |
279 | | -operating system. Download the file to a directory where the program will |
280 | | -eventually reside (see below).<p> |
281 | | -<aname="uncpga"><h2>How to uncompress PgAccess</h2> |
282 | | -PgAccess, like most applications available for download, is usually downloaded |
283 | | -in compressed format to save download time. You must uncompress these files in |
284 | | -order to use the application.<p> |
285 | | -<h3>UNIX (Linux, BSD, IRIX, Solaris, etc.)</h3> |
286 | | -The files will be compressed using "gzip" and packaged using "tar", and have |
287 | | -filenames like this:<p> |
288 | | -<samp>pgaccess-n.nn.tar.gz</samp><p> |
289 | | -Note that "n.nn" will be the version number in an actual file.<p> |
290 | | -First decide where you want to have the program. A typical location on UNIX |
291 | | -systems is<samp>/usr/local/src/<name></samp>, where <name> is the name of |
292 | | -the program. To use this location, download or move the "tar.gz" file to the |
293 | | -directory<samp>/usr/local/src</samp>. Change to that directory, and |
294 | | -uncompress the file with the command:<p> |
295 | | -<samp>tar -zxvf pgaccess-n.nn.tar.gz</samp><p> |
296 | | -You should see the files listed as they are uncompressed and placed in the new |
297 | | -directory, and now have a directory named:<p> |
298 | | -<samp>/usr/local/src/pgaccess</samp><p> |
299 | | -In that directory will be all of the files that were packaged in the downloaded |
300 | | -file. When you have PgAccess working, you can delete the file with the ".tar" |
301 | | -or ".tar.gz" extension. |
302 | | -<h3>Windows</h3> |
303 | | -The files will be compressed so that "WinZip" will uncompress the package. Just |
304 | | -open the file with "WinZip" and the program files will be extracted.<p> |
305 | | -<aname="putpga"><h2>Putting PgAccess where it will be found</h2> |
306 | | -<h3>UNIX</h3> |
307 | | -In order to run PgAccess easily, the program file "pgaccess.tcl" should be in a |
308 | | -location on the "PATH" of the system. You can find out what the PATH is by |
309 | | -entering:<p> |
310 | | -<samp>echo $PATH<br> |
311 | | -/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:./:/usr/local/pgsql/bin |
312 | | -</samp><p> |
313 | | -Usually the directory<samp>/usr/local/bin</samp> will be in your PATH, and that |
314 | | -is a fairly common place to put programs like PgAccess. Other common |
315 | | -directories in the PATH are<samp>/usr/bin</samp> and<samp>/usr/sbin</samp>. |
316 | | -Simply move the file "pgaccess.tcl" to the directory where you want it.<p> |
317 | | -<h3>Windows</h3> |
318 | | -You will usually link PgAccess to an icon, so just specify the full path to the |
319 | | -program when you create the icon. |
320 | | -<aname=startpga"><h2>Starting PgAccess</h2> |
321 | | -The easiest way to start PgAccess is to simply invoke the program by name:<p> |
322 | | -<samp>pgaccess.tcl</samp><p> |
323 | | -If the program has been placed in a directory listed in the PATH, the PgAccess |
324 | | -window should appear.<p> |
325 | | -<h3>Starting from a menu</h3> |
326 | | -Most users will want to link the program to a menu or icon so that it can be |
327 | | -started using the mouse or other pointing device. Here is a method that will |
328 | | -work on most Linux X-Windows systems. Create a file named "pgaccess" in the directory |
329 | | -<samp>/etc/X11/wmconfig</samp> with the following contents:<p> |
330 | | -<samp>pgaccess name "PgAccess"<br> |
331 | | -pgaccess description "postgreSQL frontend"<br> |
332 | | -pgaccess mini-icon "mini-pgaccess.xpm"<br> |
333 | | -pgaccess group "Applications"<br> |
334 | | -pgaccess exec "pgaccess.tcl &"</samp><p> |
335 | | -This assumes that you have an "Applications" sub-menu. You may prefer |
336 | | -"Programs" or some other place. Also, you will have to create the |
337 | | -"mini-pgaccess.xpm" icon if you want it to appear. You can edit an existing |
338 | | -icon from the<samp>/usr/share/icons/mini</samp> directory in XPaint and rename |
339 | | -it. When you next start an X-Windows session, there should be a "PgAccess" item |
340 | | -on the menu that you have chosen. Clicking on this item should start |
341 | | -PgAccess.<p> |
342 | | -<ahref="index.html#start">Back to index</a> |
343 | | -</body></html> |