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.

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)

<BR><TT></TT>&nbsp;

<BR><TT></TT>&nbsp;<TT></TT>

<P><TT>Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group</TT>

<P><TT>Portions Copyright (c) 1994, Regents of the University of California</TT>

<P><TT>Copyright (c) 1994-7 Regents of the University of California</TT><TT></TT>

<P><TT>Permission to use, copy, modify, and distribute this software and

its</TT>

<BR><TT>documentation for any purpose, without fee, and without a written

agreement</TT>

<BR><TT>is hereby granted, provided that the above copyright notice and

this</TT>

<BR><TT>paragraph and the following two paragraphs appear in all copies.</TT>

<BR><TT>paragraph and the following two paragraphs appear in all copies.</TT><TT></TT>

<P><TT>IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY

PARTY FOR</TT>

<BR><TT>LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS</TT>

<BR><TT>DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED

OF THE</TT>

<BR><TT>POSSIBILITY OF SUCH DAMAGE.</TT>

<BR><TT>POSSIBILITY OF SUCH DAMAGE.</TT><TT></TT>

<P><TT>THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,</TT>

<BR><TT>INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY</TT>

<BR><TT></TT>&nbsp;

<BR><TT></TT>&nbsp;<TT></TT>

<P><TT>Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group</TT>

<P><TT>Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group</TT>

<P><TT>Portions Copyright (c) 1994, Regents of the University of California</TT>

<P><TT>Permission to use, copy, modify, and distribute this software and

<BR><TT></TT>&nbsp;

<BR><TT></TT>&nbsp;<TT></TT>

<P><TT>Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group</TT>

<P><TT>Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group</TT>

<P><TT>Portions Copyright (c) 1994, Regents of the University of California</TT>

<P><TT>Permission to use, copy, modify, and distribute this software and

Notice that there are two consecutive tildes to allow for the fact that this

particular entry doesn't have anything in the<b>Editor</b> field.

You can then perform a<em>Query</em> as follows:<p>

<samp>COPY psyref FROM '/home/jim/newref.txt'WITH DELIMITER

<samp>COPY psyref FROM '/home/jim/newref.txt'USING DELIMITERS

'~';</samp><p>

This will read the records from<samp>newref.txt</samp> and insert them into the

table<samp>psyref</samp>. See the PostgreSQL documentation under the headings

namespace eval Database {

proc{getTablesList} {} {

global CurrentDB PgAcVar

set tlist {}

}else {

set sysconstraint""

}

wpg_select$CurrentDB"select relname from pg_class where (relkind='r')$sysconstraint order by relname" rec {

if {![info exists itsaview($rec(relname))]} {

wpg_select$CurrentDB"select relname from pg_class where (relkind='r')or (relkind='v')$sysconstraint order by relname" rec {

lappend tlist$rec(relname)

}

}

} gterrmsg]} {

showError$gterrmsg

" {} "

COPY \[ BINARY \] table \[ WITH OIDS \]

FROM { 'filename' | stdin }

\[WITH DELIMITER 'delimiter' \]

\[USING DELIMITERS 'delimiter' \]

COPY \[ BINARY \] table \[ WITH OIDS \]

TO { 'filename' | stdout }

\[WITH DELIMITER 'delimiter' \]

\[USING DELIMITERS 'delimiter' \]

" {code} "Inputs" {bold} "

" {} "Usage" {bold} "

The following example copies a table to standard output, using a vertical bar \(\"|\"\) as the field delimiter:

COPY country TO stdoutWITH DELIMITER '|';

COPY country TO stdoutUSING DELIMITERS '|';

To copy data from a Unix file into a table \"country\":

COPY country FROM '/usr1/proj/bray/sql/country_data';

The " {} "BINARY" {bold} " keyword will force all data to be stored/read as binary objects rather than as text. It is somewhat faster than the normal copy command, but is not generally portable, and the files \

generated are somewhat larger, although this factor is highly dependent on the data itself. By default, a text copy uses a tab \

\(\"\\t\"\) character as a delimiter. The delimiter may also be changed to any other single character with the keyword phraseWITH DELIMITER. Characters in data fields which happen to match the delimiter character will be quoted.

\(\"\\t\"\) character as a delimiter. The delimiter may also be changed to any other single character with the keyword phraseUSING DELIMITERS. Characters in data fields which happen to match the delimiter character will be quoted.

You must have select access on any table whose values are read by " {} "COPY" {bold} ", and either insert or update access to a table into which values are being inserted by \

" {} "COPY" {bold} ". The backend also needs appropriate Unix permissions for any file read or written by \

" {} "COPY" {bold} ".

The keyword phrase " {} "WITH DELIMITER" {bold} " specifies a single character to be used for all delimiters between columns.

The keyword phrase " {} "USING DELIMITERS" {bold} " specifies a single character to be used for all delimiters between columns. If multiple characters are specified in the delimiter string, only the first \

character is used.

Tip: Do not confuse " {} "COPY" {bold} " with the psql instruction \\copy. "

.pgaw:Help.f.t insert end \

"Copyrights\n\n" {title} \

"

PostgreSQL is Copyright � 1996-2002, PostgreSQL Global Development Group.

PostgreSQL is Copyright � 1996-2001, PostgreSQL Global Development Group.

Postgres95 is Copyright � 1994, Regents of the University of California.

.pgaw:Help.f.t insert end "The Reports module is still in alpha stage.

The module should be able to design and execute a report based on a table\

or from an existing query.

DONE:

# Allows for reports based on tables or views.

# Formulas are just Tcl evals, where column names are available as variables.

Try: concat \$colname1 \$colname2

# Pictures must be gif or bmp files (and not stored in the database).

# Page header is the first record on a page, page footer is the last.

# Detail section is all the records that can fit on a page, row by row.

# Multiple pages.

# Printing puts the report into a Postscript file.\

The pages printed are the ones in and between the boxes on preview mode.

You can also pipe the output by entering it in the dialog when prompted.\

Try: |lpr

# Page resizing can be done by typing in the Page size boxes.

# Report resizing can be done by typing in the Report size boxes and hitting\

enter or dragging the window and clicking in it with the mouse.

Grouping, sorting, subtotals, expressions should be implemented.

Report output can be printed as a Postscript file.

DOING:

# Allow for reports based on queries.

# Report headers and footers.

# Grouping, sorting, subtotals.

# Drawing simple shapes like lines or circles.

# Font choice needs expanding.

# Putting stuff into columns when the page is wider than the report.

For the moment I have no time to do that so volunteers are welcome.

Also, there are a couple Postscript items to be addressed:

# Since the Tk canvas widget outputs Encapsulated Postscript,\

each page printed is a separate piece of Encapsulated Postscript.\

Putting all those pieces together into one Postscript file was\

a bit of a kluge, so right now you get every other page blank. Doh.

# Each time a picture is displayed, the Postscript grows by about 10 times\

the size of the picture. It seems in general Postscript gets enormous\

fast, at least with the Tk canvas widget's method of outputting it.

Please send patches, proposals, problems, pickles, etc., to Chris Maj <cmaj@freedomcorpse.info> or visit pgaccess.org

"