aboutsummaryrefslogtreecommitdiff
path: root/src/bin/pgaccess/README
diff options
context:
space:
mode:
Diffstat (limited to 'src/bin/pgaccess/README')
-rw-r--r--src/bin/pgaccess/README96
1 files changed, 21 insertions, 75 deletions
diff --git a/src/bin/pgaccess/README b/src/bin/pgaccess/README
index db926dab3a0..50a2fcd443d 100644
--- a/src/bin/pgaccess/README
+++ b/src/bin/pgaccess/README
@@ -1,82 +1,28 @@
----------------------------------------------------------------------------
+Hi,
-Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group
-Portions Copyright (c) 1994, Regents of the University of California
+I've made a few changes in the pgaccess source to make it work with overloaded functions too.
-Permission to use, copy, modify, and distribute this software and its
-documentation for any purpose, without fee, and without a written agreement
-is hereby granted, provided that the above copyright notice and this
-paragraph and the following two paragraphs appear in all copies.
+The files that I changed are:
-IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR
-DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING
-LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS
-DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGE.
+ pgaccess: to run the modified version from the actual directory
+ /lib/functions.old: bugfix for working with overloaded functions, and another one: if somebody has made a mistake
+ in the editing process, the function was deleted, and recreation was not possibble, because the
+ program returned an error message. Now the error message is still persists, but the procedure
+ doesn't take this into consideration.
+ Added "Save as" button to create a new function with the same source. Very usefull when one needs
+ a new function with slight modification to the source code.
+ Then default window size is increased to let the larger source code visible without resizing.
+ /lib/mainlib.tcl: for the same bugfix, now the functionnames are represented with the parameters too, I think, that
+ the structure is more visible now. Bugfix for the introduced functionalities, at deleteing object
+ (function).
+ /lib/tables.tcl: I don't know how, but there is a difference. Maybe this is one of the misteries of the universe :)
-THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
-INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS
-ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO
-PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
+So, in spite of the fact that this "hacking" is my first juorney in the tcl scripting language, I think
+I've made a good job after all. I hope, this changes will be reflected in the future release of the pgaccess.
----------------------------------------------------------------------------
+There can be several hidden bugs introduced by the changes, if you find one of them please let me know.
+At this time I am using the changed software that helps me much more in the actual project.
-PGACCESS 0.98.7 27 January 2001
-================================
-I dedicate this program to my little daughters Ana-Maria and Emilia and to my
-wife for their understanding. I hope they will forgive me for spending so many
-time far from them.
-
-
-
-1. How to INSTALL ?
-
-You will need a Tcl/Tk package greater than 8.0
-
-For Unix users, unpack the pgaccess-xxx.tar.gz archieve in you preferred
-directory (usually /usr/local).
-
-Check where your "wish" program is and modify (if needed) the file
-/usr/local/pgaccess/pgaccess and set variables PGACCESS_HOME and
-PATH_TO_WISH to the appropriate directories.
-
-Include the /usr/local/pgaccess directory into your PATH or make a
-symbolic link to it wherever you want (in PATH directories).
-Example:
-
-$ ln -s /usr/local/pgaccess/pgaccess /usr/bin/pgaccess
-
-You will find also some documentation and FAQ in the doc directory.
-
-
-
-2. Usage
-
-You run it with the command:
-
- pgaccess [database]
-
-[database] is optional.
-
-
-
-3. Bug reporting
-
-First of all : operating system, PostgreSQL version,Tcl/Tk version.
-A more detailed story of what have you done when error occurred.
-Tcl/Tk stops usually with a error message and there is a button there
-"Stack Trace" and if you press it, you will see a detailed information
-about the procedure containing the error. Please send it to me.
-Some information about table structure, no. of fields, records would
-be also good.
-
-===========================================================================
-You would find always the latest version at http://www.flex.ro/pgaccess
-
-Please feel free to e-mail me with any suggestion or bug description
-that will help to improve it.
-
-Constantin Teodorescu <teo@flex.ro>
-
+Best regards,
+Bartus Levente (bartus.l at bitel.hu) \ No newline at end of file