pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Undeliverable Message
30+ messages / 1 participants
[nested] [flat]

* Undeliverable Message
@ 1999-02-12 08:08 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-02-12 08:08 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #224

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest  Thursday, February 11 1999  Volume 01 : Number 224



Index:

[none]
Re: [INTERFACES] libpq and multi-threading on Linux?
Troubles with the ODBC driver in the postgres distribution (integrated installation)
Troubles with the ODBC driver in the postgres distribution (integrated installation)
Troubles with the ODBC driver in the postgres distribution (integrated installation)
Troubles with the ODBC driver in the postgres distribution (standalone installation)
ODBC - MSysConf
[none]
pgAdmin v6.4.2
Re: [INTERFACES] facing problem with ecpg
Re: [INTERFACES] ODBC - MSysConf
JDBC: DatabaseMetaData and getPrimaryKeys
Re: [INTERFACES] facing problem with ecpg
Re: [INTERFACES] JDBC: DatabaseMetaData and getPrimaryKeys
Help with ODBC
Help with ODBC in VB6

----------------------------------------------------------------------

Date: Thu, 11 Feb 1999 09:42:04 +0200
From: "Sergey T. Soenko" <serg@kzsm.lg.ua>
Subject: [none]

- -- 
< ++++˜+mailto:serg@kzsm.lg.ua

------------------------------

Date: Thu, 11 Feb 1999 01:59:37 -0700
From: Brendan Rempel <rempelb@cybersurf.net>
Subject: Re: [INTERFACES] libpq and multi-threading on Linux?

I succeeded in doing exactly that.  I simply took the C source examples on
the Postgres documentation and pasted it into the thread with no problems
at all.  The only changes made to the examples were just simple ones like
return values or fprintf(stderr) stuff, but that's all. Postgres server
and libpq libraries run flawlessly in pthreads.

For me, synchronization was not required since each thread did not share
resources with other threads.  Each thread personally initialized the
libpq connection, did its job and destroyed the connection, just like the
example.

Brendan

Michael Olivier wrote:

> Hi folks,
>
> I apologize in advance if I have overlooked docs, but I haven't been
> able to find a discussion of how PostGreSQL via libpq on Linux fares
> with pthreads. Can someone point me to docs if available, or otherwise
> enlighten me? How well does it work and what are the important design
> issues to consider?
>
> I'm expecting to create a pool of db connections to use within a
> long-running process, which will create a new thread for each incoming
> request from a client. I've found just a very little bit about PG
> being multi-processing, but not how it will interact with a
> multi-threaded client. I appreciate your comments.
>
> thanks,
> --Michael
>
> _________________________________________________________
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com

------------------------------

Date: Thu, 11 Feb 1999 10:48:26 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (integrated installation)

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- -----------------------------------------------
My compilations for integrated installation:



1> integrated installation with a GNU c++
 ./configure --prefix- --with-template- --with-CXX


gmake
...
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
/usr/local/geoscope/src/GNU/package/usr/local/bin/c++  -I../../backend
- -I../../include -I../../interfaces/libpq -I../../include
- -I../../backend   -Xa -v -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO
- -K PIC   -c pgenv.cc -o pgenv.o
c++: cannot specify -o with -c and multiple compilations
gmake[2]: *** [pgenv.o] Error 1
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2



2> integrated installation with /opt/SUNWspro/bin/CC (workshop, solaris)



 ./configure --prefix- --with-template
gmake

gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
CC  -I../../backend -I../../include -I../../interfaces/libpq
- -I../../include -I../../backend   -Xa -v -D__sparc__ -D__sun__
- -DDISABLE_COMPLEX_MACRO  -K PIC   -c pgenv.cc -o pgenv.o
CC: Warning: Option -Xa passed to ld, if ld is invoked, ignored
otherwise
CC: Warning: Option -K passed to ld, if ld is invoked, ignored otherwise

### CC: Note: LM_LICENSE_FILE ### CC: Note: NLSPATH /opt/SUNWspro/bin/../SC4.2/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/SUNWspro/bin/../SC4.2/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat

CC: Invalid input file name PIC, no output generated for this file.
/opt/SUNWspro/bin/../SC4.2/bin/ccfe -y-o -ypgenv.o -I../../backend
- -I../../include -I../../interfaces/libpq -I../../include -I../../backend
- -y-fbe -y/opt/SUNWspro/bin/../SC4.2/bin/fbe -ptb pgenv.o -y-xarch- -y-verbose -O0 -ptf /tmp/08458%1.%2 -ptx
/opt/SUNWspro/bin/../SC4.2/bin/CC -ptk "-I../../backend -I../../include
- -I../../interfaces/libpq -I../../include -I../../backend -Xa -v
- -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO -K -c " -D__SunOS_5_6
- -D__SUNPRO_CC20 -Dunix -Dsun -Dsparc -D__sparc -D__unix -D__sun
- -D__BUILTIN_VA_ARG_INCR -D__SVR4 -I/opt/SUNWspro/SC4.2/include/CC
- -I/opt/SUNWspro/SC4.2/include/CC/rw7 -I/opt/SUNWspro/SC4.2/include/cc
- -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO pgenv.cc -s
/tmp/ccfe.08458.0.s
"pgenv.h", line 21: Error: Could not open include file <string>.
"pgenv.h", line 25: Error: Type name expected instead of "using".
"pgenv.h", line 48: Error: Type name expected instead of "string".
"pgenv.h", line 48: Error: No storage class or type for this
declaration.
"pgenv.h", line 48: Error: "," expected instead of "pgAuth".
"pgenv.h", line 49: Error: Use ";" to terminate declarations.
"pgenv.h", line 49: Error: Type name expected instead of "string".
"pgenv.h", line 49: Error: No storage class or type for this
declaration.
"pgenv.h", line 49: Error: Multiple declaration for string.
"pgenv.h", line 49: Error: "," expected instead of "pgHost".
"pgenv.h", line 50: Error: Use ";" to terminate declarations.
"pgenv.h", line 50: Error: Type name expected instead of "string".
"pgenv.h", line 50: Error: No storage class or type for this
declaration.
"pgenv.h", line 50: Error: Multiple declaration for string.
"pgenv.h", line 50: Error: "," expected instead of "pgPort".
"pgenv.h", line 51: Error: Use ";" to terminate declarations.
"pgenv.h", line 51: Error: Type name expected instead of "string".
"pgenv.h", line 51: Error: No storage class or type for this
declaration.
"pgenv.h", line 51: Error: Multiple declaration for string.
"pgenv.h", line 51: Error: "," expected instead of "pgOption".
"pgenv.h", line 52: Error: Use ";" to terminate declarations.
"pgenv.h", line 52: Error: Type name expected instead of "string".
"pgenv.h", line 52: Error: No storage class or type for this
declaration.
"pgenv.h", line 52: Error: Multiple declaration for string.
"pgenv.h", line 52: Error: "," expected instead of "pgTty".
Compilation aborted, too many Error messages.
rm /tmp/ccfe.08458.0.s
gmake[2]:







How can I fix the problem?
What is the mistake?

thank you for answering :)



Pascal

------------------------------

Date: Thu, 11 Feb 1999 10:57:21 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (integrated installation)

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- -----------------------------------------------
My compilations for integrated installation:

1> integrated installation with a GNU c++
 ./configure --prefix- --with-template- --with-CXX
gmake
...
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
/usr/local/geoscope/src/GNU/package/usr/local/bin/c++  -I../../backend
- -I../../include -I../../interfaces/libpq -I../../include
- -I../../backend   -Xa -v -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO
- -K PIC   -c pgenv.cc -o pgenv.o
c++: cannot specify -o with -c and multiple compilations
gmake[2]: *** [pgenv.o] Error 1
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2

2> integrated installation with /opt/SUNWspro/bin/CC (workshop, solaris)

 ./configure --prefix- --with-template
gmake

gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
CC  -I../../backend -I../../include -I../../interfaces/libpq
- -I../../include -I../../backend   -Xa -v -D__sparc__ -D__sun__
- -DDISABLE_COMPLEX_MACRO  -K PIC   -c pgenv.cc -o pgenv.o
CC: Warning: Option -Xa passed to ld, if ld is invoked, ignored
otherwise
CC: Warning: Option -K passed to ld, if ld is invoked, ignored otherwise

### CC: Note: LM_LICENSE_FILE ### CC: Note: NLSPATH /opt/SUNWspro/bin/../SC4.2/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/SUNWspro/bin/../SC4.2/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat

CC: Invalid input file name PIC, no output generated for this file.
/opt/SUNWspro/bin/../SC4.2/bin/ccfe -y-o -ypgenv.o -I../../backend
- -I../../include -I../../interfaces/libpq -I../../include -I../../backend
- -y-fbe -y/opt/SUNWspro/bin/../SC4.2/bin/fbe -ptb pgenv.o -y-xarch- -y-verbose -O0 -ptf /tmp/08458%1.%2 -ptx
/opt/SUNWspro/bin/../SC4.2/bin/CC -ptk "-I../../backend -I../../include
- -I../../interfaces/libpq -I../../include -I../../backend -Xa -v
- -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO -K -c " -D__SunOS_5_6
- -D__SUNPRO_CC20 -Dunix -Dsun -Dsparc -D__sparc -D__unix -D__sun
- -D__BUILTIN_VA_ARG_INCR -D__SVR4 -I/opt/SUNWspro/SC4.2/include/CC
- -I/opt/SUNWspro/SC4.2/include/CC/rw7 -I/opt/SUNWspro/SC4.2/include/cc
- -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO pgenv.cc -s
/tmp/ccfe.08458.0.s
"pgenv.h", line 21: Error: Could not open include file <string>.
"pgenv.h", line 25: Error: Type name expected instead of "using".
"pgenv.h", line 48: Error: Type name expected instead of "string".
"pgenv.h", line 48: Error: No storage class or type for this
declaration.
"pgenv.h", line 48: Error: "," expected instead of "pgAuth".
"pgenv.h", line 49: Error: Use ";" to terminate declarations.
"pgenv.h", line 49: Error: Type name expected instead of "string".
"pgenv.h", line 49: Error: No storage class or type for this
declaration.
"pgenv.h", line 49: Error: Multiple declaration for string.
"pgenv.h", line 49: Error: "," expected instead of "pgHost".
"pgenv.h", line 50: Error: Use ";" to terminate declarations.
"pgenv.h", line 50: Error: Type name expected instead of "string".
"pgenv.h", line 50: Error: No storage class or type for this
declaration.
"pgenv.h", line 50: Error: Multiple declaration for string.
"pgenv.h", line 50: Error: "," expected instead of "pgPort".
"pgenv.h", line 51: Error: Use ";" to terminate declarations.
"pgenv.h", line 51: Error: Type name expected instead of "string".
"pgenv.h", line 51: Error: No storage class or type for this
declaration.
"pgenv.h", line 51: Error: Multiple declaration for string.
"pgenv.h", line 51: Error: "," expected instead of "pgOption".
"pgenv.h", line 52: Error: Use ";" to terminate declarations.
"pgenv.h", line 52: Error: Type name expected instead of "string".
"pgenv.h", line 52: Error: No storage class or type for this
declaration.
"pgenv.h", line 52: Error: Multiple declaration for string.
"pgenv.h", line 52: Error: "," expected instead of "pgTty".
Compilation aborted, too many Error messages.
rm /tmp/ccfe.08458.0.s
gmake[2]:

How can I fix the problem?
What is the mistake?

thank you for answering :)

Pascal

------------------------------

Date: Thu, 11 Feb 1999 11:15:14 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (integrated installation)

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- -----------------------------------------------
My compilations for integrated installation:

1> integrated installation with a GNU c++
 ./configure --prefix- --with-template- --with-CXX
gmake
...
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
/usr/local/geoscope/src/GNU/package/usr/local/bin/c++  -I../../backend
- -I../../include -I../../interfaces/libpq -I../../include
- -I../../backend   -Xa -v -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO
- -K PIC   -c pgenv.cc -o pgenv.o
c++: cannot specify -o with -c and multiple compilations
gmake[2]: *** [pgenv.o] Error 1
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2

2> integrated installation with /opt/SUNWspro/bin/CC (workshop, solaris)

 ./configure --prefix- --with-template
gmake

gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
CC  -I../../backend -I../../include -I../../interfaces/libpq
- -I../../include -I../../backend   -Xa -v -D__sparc__ -D__sun__
- -DDISABLE_COMPLEX_MACRO  -K PIC   -c pgenv.cc -o pgenv.o
CC: Warning: Option -Xa passed to ld, if ld is invoked, ignored
otherwise
CC: Warning: Option -K passed to ld, if ld is invoked, ignored otherwise

### CC: Note: LM_LICENSE_FILE ### CC: Note: NLSPATH /opt/SUNWspro/bin/../SC4.2/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/SUNWspro/bin/../SC4.2/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat

CC: Invalid input file name PIC, no output generated for this file.
/opt/SUNWspro/bin/../SC4.2/bin/ccfe -y-o -ypgenv.o -I../../backend
- -I../../include -I../../interfaces/libpq -I../../include -I../../backend
- -y-fbe -y/opt/SUNWspro/bin/../SC4.2/bin/fbe -ptb pgenv.o -y-xarch- -y-verbose -O0 -ptf /tmp/08458%1.%2 -ptx
/opt/SUNWspro/bin/../SC4.2/bin/CC -ptk "-I../../backend -I../../include
- -I../../interfaces/libpq -I../../include -I../../backend -Xa -v
- -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO -K -c " -D__SunOS_5_6
- -D__SUNPRO_CC20 -Dunix -Dsun -Dsparc -D__sparc -D__unix -D__sun
- -D__BUILTIN_VA_ARG_INCR -D__SVR4 -I/opt/SUNWspro/SC4.2/include/CC
- -I/opt/SUNWspro/SC4.2/include/CC/rw7 -I/opt/SUNWspro/SC4.2/include/cc
- -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO pgenv.cc -s
/tmp/ccfe.08458.0.s
"pgenv.h", line 21: Error: Could not open include file <string>.
"pgenv.h", line 25: Error: Type name expected instead of "using".
"pgenv.h", line 48: Error: Type name expected instead of "string".
"pgenv.h", line 48: Error: No storage class or type for this
declaration.
"pgenv.h", line 48: Error: "," expected instead of "pgAuth".
"pgenv.h", line 49: Error: Use ";" to terminate declarations.
"pgenv.h", line 49: Error: Type name expected instead of "string".
"pgenv.h", line 49: Error: No storage class or type for this
declaration.
"pgenv.h", line 49: Error: Multiple declaration for string.
"pgenv.h", line 49: Error: "," expected instead of "pgHost".
"pgenv.h", line 50: Error: Use ";" to terminate declarations.
"pgenv.h", line 50: Error: Type name expected instead of "string".
"pgenv.h", line 50: Error: No storage class or type for this
declaration.
"pgenv.h", line 50: Error: Multiple declaration for string.
"pgenv.h", line 50: Error: "," expected instead of "pgPort".
"pgenv.h", line 51: Error: Use ";" to terminate declarations.
"pgenv.h", line 51: Error: Type name expected instead of "string".
"pgenv.h", line 51: Error: No storage class or type for this
declaration.
"pgenv.h", line 51: Error: Multiple declaration for string.
"pgenv.h", line 51: Error: "," expected instead of "pgOption".
"pgenv.h", line 52: Error: Use ";" to terminate declarations.
"pgenv.h", line 52: Error: Type name expected instead of "string".
"pgenv.h", line 52: Error: No storage class or type for this
declaration.
"pgenv.h", line 52: Error: Multiple declaration for string.
"pgenv.h", line 52: Error: "," expected instead of "pgTty".
Compilation aborted, too many Error messages.
rm /tmp/ccfe.08458.0.s
gmake[2]:

How can I fix the problem?
What is the mistake?

thank you for answering :)

Pascal

------------------------------

Date: Thu, 11 Feb 1999 12:06:34 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (standalone installation)

- --------------668455E0634BA07049CA63EA
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- -----------------------------------------------
My compilations for standalone installation:

1> standalone installation with a GNU c++


cd interfaces/odbc

gmake standalone

rm -f psqlodbc-025.tar.gz
/bin/tar -chf psqlodbc-025.tar \
    *.c *.h *.in Config.mk TODO.txt Version.mk config.guess config.sub
configure install-sh license.txt notice.txt odbcinst.ini psqlodbc.def
psqlodbc.rc readme.txt -C ../.. makefiles template Makefile.shlib
tar: Makefile.shlib: No such file or directory
gmake: *** [standalone] Error 1
[root@geosp15]tcsh(14)





How can I fix the problem?
What is the mistake?

thank you for answering :)

Pascal




- --

- -------------------------------------------
        Pascal  DAYRE

        dayre@ipgp.jussieu.fr
        tel:    (33) 1 44 27 38 96
        fax:    (33) 1 44 27 38 94
- --------------------------------------------



- --------------668455E0634BA07049CA63EA
Content-Type: text/html; charsetContent-Transfer-Encoding: 7bit

<HTML>
(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

<P>Hello everybody, can you help me?

<P>I 've tried to install the ODBC driver like the description
<BR>in "PostgreSQL Programmer's Guide" guide (153-157).
<BR>I've tried the integrated installation and also the standalone
<BR>installation.

<P>What is the compiler needed for C++? I have tried a GNU one and a
<BR>Solaris one?
<BR>What is the good version for GNU C++?

<P>-----------------------------------------------
<BR>My compilations for standalone installation:

<P>1> standalone installation with a GNU c++
<BR>&nbsp;

<P>cd interfaces/odbc

<P>gmake standalone

<P>rm -f psqlodbc-025.tar.gz
<BR>/bin/tar -chf psqlodbc-025.tar \
<BR>&nbsp;&nbsp;&nbsp; *.c *.h *.in Config.mk TODO.txt Version.mk config.guess
config.sub configure install-sh license.txt notice.txt odbcinst.ini psqlodbc.def
psqlodbc.rc readme.txt -C ../.. makefiles template Makefile.shlib
<BR>tar: Makefile.shlib: No such file or directory
<BR>gmake: *** [standalone] Error 1
<BR>[root@geosp15]tcsh(14)
<BR>&nbsp;
<BR>&nbsp;
<BR>&nbsp;
<BR>&nbsp;

<P>How can I fix the problem?
<BR>What is the mistake?

<P>thank you for answering :)

<P>Pascal
<BR>&nbsp;
<BR>&nbsp;
<BR>&nbsp;
<PRE>--&nbsp;


- -------------------------------------------
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pascal&nbsp; DAYRE

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dayre@ipgp.jussieu.fr
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tel:&nbsp;&nbsp;&nbsp; (33) 1 44 27 38 96
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fax:&nbsp;&nbsp;&nbsp; (33) 1 44 27 38 94
- --------------------------------------------</PRE>
&nbsp;</HTML>

- --------------668455E0634BA07049CA63EA--

------------------------------

Date: Thu, 11 Feb 1999 12:59:49 -0800
From: Karsten Kaus <kk@kdschmid.de>
Subject: ODBC - MSysConf

ok, in general it seems to be possible to connect Access97 ( not Access
2.0! ?right?  ) to postgres.
It works on ONE of my Computers in the office (486). On that computer
I cannot start the 32Bit-ODBC in the systemconfiguration, but I can
create DSNs within Access97, and I get connected to any postgres-
database I wish (tried only 2).
On my Pentium in the office and on ALL machines at home I get the 
error 4307, that there is a Table called MSysConf on my server but
it does not have the expected format.
I searched for this table using grep and pg_dumpall as well as psql \dS
and could not find anything. So I created one as described in the
MSAccess-Help, but this didn't help. Still the fomat was invalid.
I do not want to use this table anyway ( do I? ), so what to do?

Thanks for help,
Karsten Kaus

------------------------------

Date: Thu, 11 Feb 1999 14:09:24 +0100
From: Andreas Kaschke <kaschke@books.de>
Subject: [none]

subscribe

------------------------------

Date: Thu, 11 Feb 1999 16:06:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: pgAdmin v6.4.2

I've just released pgAdmin v6.4.2 which is available from:

http://www.vale-it.demon.co.uk/freeware

New features/enhancements include:

1) Improved the error logging to include details of the database connection
and some internal variables in the logfile.
2) Added a check to prevent use with earlier  versions of PostgreSQL than
are compatible.
3) Added checks to warn the user if the ODBC driver settings for the
datasource could cause problems with the operation of pgAdmin.
4) Added a Database browser dialogue with Create and Drop database
facilities.

Please note that pgAdmin 6.4.x will only work correctly with PostgreSQL
6.4.x.

Regards,

Dave.
- --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!

------------------------------

Date: Fri, 12 Feb 1999 00:42:34 +0800
From: hoelc <hoelc@pd.jaring.my>
Subject: Re: [INTERFACES] facing problem with ecpg

Hello,
I've just upgrated my PostgreSQL system to version Postgres-6.4.2
Now it has the *ecpg
But I'm facing problem in using it, when I compile the C program with
        cc -o tryecpg tryecpg.c -lecpg -lpq
the compiler can't recognize the " exec sql ", and give error massage
       Parse error before 'sql'

What went wrong ?  Please advise.
Thanks for giving me the address for the Oracle Pre*C/C++ programmer's guide, it
is a good reference.  But, it doesn't exactly reflect the ecpg, right?  Is there
any reference and example program for how to use ecpg?
Thank you very much.

Regards,
LCH

Michael Meskes wrote:

> On Sat, Feb 06, 1999 at 07:16:14PM -0600, James Thompson wrote:
> > http://www.dal.ca/%7eoracle/oradoc/DOC/api/doc/PC_22/toc.htm
>
> Gotta look at this.
>
> > With it you end up with something like the following in your code
> >
> >     exec sql
> >       insert into customer(id,name_first,name_middle,name_last,company,
> >                       address1,address2,city,state,country,zip,phone_work,
> >                       phone_home,phone_fax,email,date_entered,billing_terms,
> >                            confirmation_method)
> >       values (:id,:name_first, :name_middle, :name_last,
> >               :company,:address1,:address2,
> >               :city,:state,:country,:zip,:phone_work,
> >               :phone_home,:phone_fax,:email,date('now'),
> >               :billing_terms,
> >               :confirmation_method);
>
> Xou can even add indicators like in
>
> ... values (:id,:name_first, :name_middle:nm_ind, :name_last, ...
>
> If nm_ind is set to -1 the name_middle entry will be set to NULL.
>
> > The author of the code is very responsive to few problem reports I have
> > sent him and has sent patches, or workarounds to me usually within 24
> > hours.
>
> Glad I can help. :-)
>
> > In the few cases you can't figure out a way to make something happen using
> > ecpg I believe you can mix the libpg and ecpg code in the same program.
> > The only place I could see a need for this is when you'd need the
> > functionality given by Pro*C's Dynamic SQL which ecpg doesn't yet support,
> > but I think its in the works.
>
> It is. In fact I already submitted a patch for the PREPARE and EXECUTE
> commands. James, if you'd like to test this I can send you the source until
> it makes its way into CVS.
>
> Michael
> --
> Michael Meskes                         | Go SF 49ers!
> Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
> Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
> Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

Date: Thu, 11 Feb 1999 09:35:12 -0500
From: David Hartwig <daveh@insightdist.com>
Subject: Re: [INTERFACES] ODBC - MSysConf

Karsten Kaus wrote:

> ok, in general it seems to be possible to connect Access97 ( not Access
> 2.0! ?right?  ) to postgres.

I recall someone doing this successfully.  The key here is that it needs to
be running on Win95, Win98, or NT.

>
> It works on ONE of my Computers in the office (486). On that computer
> I cannot start the 32Bit-ODBC in the systemconfiguration, but I can
> create DSNs within Access97, and I get connected to any postgres-
> database I wish (tried only 2).
> On my Pentium in the office and on ALL machines at home I get the
> error 4307, that there is a Table called MSysConf on my server but
> it does not have the expected format.

You do not need this table on the server.  The driver will report it as an
error in the log file, but it should not be a problem to the application.

Activate the CommLog in the driver settings and send a copy of the errant
session.  Its located in C:\psqlodbc*.log.

>
> I searched for this table using grep and pg_dumpall as well as psql \dS
> and could not find anything. So I created one as described in the
> MSAccess-Help, but this didn't help. Still the fomat was invalid.
> I do not want to use this table anyway ( do I? ), so what to do?
>

I would drop the table unless you know what you are doing with MSysConf. At
least until you get on solid footing.   It's improper configuration may
cause other problems.

------------------------------

Date: Thu, 11 Feb 1999 20:36:06 +0100
From: "Alejandro Alberola Arias" <alberola@bio.es>
Subject: JDBC: DatabaseMetaData and getPrimaryKeys

Hi,

I am using PostgreSQL 6.4 on a Linux box and its JDBC driver.

The problem is that the getPrimaryKeys() method of the
DatabaseMetaData class doesn't work for me. 

Any ideas ?

Thanks.

Alejandro Alberola
alberola@bio.es

------------------------------

Date: Thu, 11 Feb 1999 20:51:42 +0100
From: Michael Meskes <Michael.Meskes@gmx.net>
Subject: Re: [INTERFACES] facing problem with ecpg

On Fri, Feb 12, 1999 at 12:42:34AM +0800, hoelc wrote:
> Hello,
> I've just upgrated my PostgreSQL system to version Postgres-6.4.2
> Now it has the *ecpg
> But I'm facing problem in using it, when I compile the C program with
>         cc -o tryecpg tryecpg.c -lecpg -lpq
> the compiler can't recognize the " exec sql ", and give error massage
>        Parse error before 'sql'

The exec sql should be there after running ecpg. ecpg is a preprocessor. You
have to feed you're source (should be named file.pgc BTW) through ecpg
before running cc. That is:

ecpg tryecpg.pgc
cc -o tryecpg tryecpg.c -lecpg -lpq

> What went wrong ?  Please advise.

If this was not the problem we need more details.

> Thanks for giving me the address for the Oracle Pre*C/C++ programmer's guide, it
> is a good reference.  But, it doesn't exactly reflect the ecpg, right?  Is there
> any reference and example program for how to use ecpg?

The reference is pretty outdated but the source comes with three examples.
Oracle's Pro*C manual however is a good reference for the syntac of embedded
SQL, although it does not comply with the standard on some parts.

Michael
- -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

Date: Thu, 11 Feb 1999 14:31:15 -0600
From: "John Barrett" <jbarrett@onramp.net>
Subject: Re: [INTERFACES] JDBC: DatabaseMetaData and getPrimaryKeys

This is a multi-part message in MIME format.

- ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

I've attached a quick and dirty little application in Java I use to transfer
data from one server to another
It uses the getPrimaryKeys call and works nicely... please excuse the lack
of documentation/comments :)))))

Might help ya to see a working app that uses the method.....

- -----Original Message-----
From: Alejandro Alberola Arias <alberola@bio.es>
To: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Date: Thursday, February 11, 1999 1:39 PM
Subject: [INTERFACES] JDBC: DatabaseMetaData and getPrimaryKeys


>Hi,
>
>I am using PostgreSQL 6.4 on a Linux box and its JDBC driver.
>
>The problem is that the getPrimaryKeys() method of the
>DatabaseMetaData class doesn't work for me.
>
>Any ideas ?
>
>Thanks.
>
>Alejandro Alberola
>alberola@bio.es
>
>
>
>

- ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
import java.sql.*;
import java.util.Vector;

class DBLogin
{
	public	String	username;
	public	String	password;
	public	String	connurl;
	
	public DBLogin(String u, String p, String c)
	{
		username = u;
		password = p;
		connurl = c;
	}
}

class DBField
{
	public	int	fnum;
	public	int	ftyp;
	public	int	fsiz;
	public	int	fdig;
	public	String	fnam;
	public	String	fdef;
	
	public DBField(ResultSet res) throws SQLException
	{
		fnum = res.getInt(17);
		ftyp = res.getInt(5);
		fsiz = res.getInt(7);
		fdig = res.getInt(9);
		ftyp = res.getInt(5);
		fnam = res.getString(4).toLowerCase();
		fdef = res.getString(6);
	
		if (fdef.equals("VARCHAR2")) {
			fdef = "VARCHAR";
		}
		
		if (fdef.equals("DATE")) {
			fdef = "DATETIME";
		}
		
		if (fdef.equals("VARCHAR")) {
			fdef = fdef + "(" + fsiz + ")";
		}
		if (fdef.equals("NUMBER")) {
			if (fdig == 0) {
				// integer
				fdef = "int4";
			} else {
				if (fdig == 2) {
					fdef = "money";
				} else {
					fdef = "decimal(" + fsiz + "," + fdig + ")";
				}
			}
		}
		fdef = fdef.toLowerCase();
	}
	
	public String toString()
	{
		return fnam + " " + fdef;
	}
}
			
class DBXfer
{
	Connection	srcConn;
	Connection	dstConn;
	DBLogin		srcLogin;
	DBLogin		dstLogin;

	public static void main(String argv[])
	{
		try {
			Class.forName ("oracle.jdbc.driver.OracleDriver");
			DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
	
			Class.forName ("postgresql.Driver");
			DriverManager.registerDriver (new postgresql.Driver());
		} catch (Exception e) {
			System.out.println("Cound Not Register Drivers");
			return;
		}

		DBLogin	srcLogin = new DBLogin("user","pass","jdbc:oracle:thin:@<host>:1521:ORCL");
		DBLogin	dstLogin = new DBLogin("user","pass","jdbc:postgresql://<host>/<db>");
		DBXfer dbx = new DBXfer(srcLogin,dstLogin);
		
		dbx.transfer(null,"schema","table");
	}
	
	public DBXfer(DBLogin src, DBLogin dst)
	{
		srcLogin = src;
		dstLogin = dst;
		
		try {
			srcConn = DriverManager.getConnection(src.connurl,src.username,src.password);
		} catch (Exception e) {
			System.out.println("Could not open source connection: " + e);
			return;
		}
		try {
			dstConn = DriverManager.getConnection(dst.connurl,dst.username,dst.password);
		} catch (Exception e) {
			System.out.println("Could not open destination connection: " + e);
			srcConn = null;
			return;
		}
	}

	public void transfer(String catalog, String schema, String table)
	{
		ResultSet	res;
		String		srcsql;
		String		dstsql;
		String		pkey[];
		int		pmax;
		DBField		fdat[];
		int		fmax;
		int		i;
		String		com;

		srcsql = "create table " + table.toLowerCase() + " ( ";
		dstsql = "insert into " + table.toLowerCase() + " ( ";
		com = "";
		pmax = 0;
		pkey = new String[16];
		fmax = 0;
		fdat = new DBField[100];

		try {
			DatabaseMetaData dmd = srcConn.getMetaData();
			
			res = dmd.getColumns(catalog,schema,table,"%");
			while (res.next()) {
				DBField	tmp = new DBField(res);
				fdat[tmp.fnum] = tmp;
				if (tmp.fnum > fmax) {
					fmax = tmp.fnum;
				}
			}
			
			for (i=1;i<fmax+1;i++) {
				srcsql = srcsql + com + fdat[i].toString();
				dstsql = dstsql + com + fdat[i].fnam;
				com = ", ";
			}

			res = dmd.getPrimaryKeys(catalog,schema,table);
			while (res.next()) {
				//System.out.println("Primary("+res.getString(5)+"): " + res.getString(4));
				pkey[res.getInt(5)] = res.getString(4);
				if (res.getInt(5) > pmax) {
					pmax = res.getInt(5);
				}
			}
			if (pmax > 0) { // got a primary key
				srcsql = srcsql + com + "primary key ( ";
				com = "";
				for (i=1; i<pmax+1;i++) {
					srcsql = srcsql + com + pkey[i].toLowerCase();;
					com = ", ";
				}
				srcsql = srcsql + " )";
			}

			srcsql = srcsql + " )";
			System.out.println(srcsql);
			
			// finish building destination insert statement
			dstsql = dstsql + " ) values ( ";
			com = "";
			for (i=1;i<fmax+1;i++) {
				dstsql = dstsql + com + "?";
				com = ", ";
			}
			dstsql = dstsql + " )";
			System.out.println(dstsql);
						
			// we got everything we need.... lets do something with it !!
			Statement dstcmd = dstConn.createStatement();
			
			// drop the table if it exists
			try {
				dstcmd.executeUpdate("drop table " + table);
			} catch (Exception e) {}
			
			// create table using the definition we just assembled
			System.out.println("creating table");
			System.out.flush();
			dstcmd.executeUpdate(srcsql);
			
			// we got a table.... get the data
			Statement srccmd = srcConn.createStatement();
			System.out.println("accessing source data");
			System.out.flush();
			res = srccmd.executeQuery("select * from " + table);
			
			// setup to store data to new table
			System.out.println("building insert statement");
			System.out.flush();
			PreparedStatement dstins = dstConn.prepareStatement(dstsql);
			
			// move that data !!
			int cnt = 0;
			String fld;
			while (res.next()) {
				System.out.println("======== Record: " + (++cnt));
				System.out.flush();
				for (i=1;i<fmax+1;i++) {
					fld = res.getString(i);
					if (fld == null) {
						System.out.println(i + "\t" + fdat[i].ftyp + "\t" + fdat[i].fdig + "\t" + null);
					} else {
						System.out.println(i + "\t" + fdat[i].ftyp + "\t" + fdat[i].fdig + "\t" + fld.toString());
					}
					System.out.flush();
					if (fld == null) {
						dstins.setNull(i,fdat[i].ftyp);
					} else {
						dstins.setString(i,fld);
					}
				}
				dstins.executeUpdate();
			}
			
		} catch (Exception e) {
			System.out.println("Exception: " + e);
		}
	}
}
- ------
------------------------------

Date: Thu, 11 Feb 1999 17:59:29 -0500
From: "Stephen Turner" <stephen@edtechnews.com>
Subject: Help with ODBC

This is a multi-part message in MIME format.

- ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: quoted-printable

subscribe me


I have Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect through the internet with ODBC. I'm currently working on a project with Visual Basic where I can connect to Postgres and edit the database. I did edit the pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight and I notice in the configuration help that it refered to something else besides the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is how do I know when I'm connected through ODBC because I can't tell.

Thanks in advance

Stephen Turner
stephen@edtechnews.com

- ------Content-Type: text/html;
	charsetContent-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META content='"MSHTML 4.72.3110.7"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>subscribe me</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>I have Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect 
through the internet with ODBC. I'm currently working on a project with Visual 
Basic where I can connect to Postgres and edit the database. I did edit the 
pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight 
and I notice in the configuration help that it refered to something else besides 
the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is 
how do I know when I'm connected through ODBC because I can't tell.</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>Thanks in advance</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>Stephen Turner</FONT></DIV>
<DIV><FONT size=2><A 
href="mailto:stephen@edtechnews.com">stephen@edtechnews.com</A></FONT></DIV></BODY></HTML>

- ------
------------------------------

Date: Thu, 11 Feb 1999 18:04:00 -0500
From: "Stephen Turner" <stephen@edtechnews.com>
Subject: Help with ODBC in VB6

This is a multi-part message in MIME format.

- ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: quoted-printable

subscribe

I have Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect through the internet with ODBC. I'm currently working on a project with Visual Basic where I can connect to Postgres and edit the database. I did edit the pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight and I notice in the configuration help that it refered to something else besides the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is how do I know when I'm connected through ODBC because I can't tell.
 
Thanks in advance
 
Stephen Turner
stephen@edtechnews.com

- ------Content-Type: text/html;
	charsetContent-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META content='"MSHTML 4.72.3110.7"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>
<DIV><FONT size=2></FONT><FONT color=#000000 size=2>subscribe</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>I have Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect 
through the internet with ODBC. I'm currently working on a project with Visual 
Basic where I can connect to Postgres and edit the database. I did edit the 
pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight 
and I notice in the configuration help that it refered to something else besides 
the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is 
how do I know when I'm connected through ODBC because I can't tell.</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>Thanks in advance</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT size=2>Stephen Turner</FONT></DIV>
<DIV><FONT size=2><A 
href="mailto:stephen@edtechnews.com">stephen@edtechnews.com</A></FONT></DIV></DIV></BODY></HTML>

- ------
------------------------------

End of pgsql-interfaces-digest V1 #224
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-02-12 09:18 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-02-12 09:18 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #226

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Friday, February 12 1999   Volume 01 : Number 226



Index:

Re: [INTERFACES] facing problem with ecpg
Re: [INTERFACES] facing problem with ecpg
Undeliverable Message

----------------------------------------------------------------------

Date: Fri, 12 Feb 1999 07:06:52 +0100
From: Michael Meskes <Michael_Meskes@topmail.de>
Subject: Re: [INTERFACES] facing problem with ecpg

On Fri, Feb 12, 1999 at 12:42:34AM +0800, hoelc wrote:
> Hello,
> I've just upgrated my PostgreSQL system to version Postgres-6.4.2
> Now it has the *ecpg
> But I'm facing problem in using it, when I compile the C program with
>         cc -o tryecpg tryecpg.c -lecpg -lpq
> the compiler can't recognize the " exec sql ", and give error massage
>        Parse error before 'sql'

The exec sql should be there after running ecpg. ecpg is a preprocessor. You
have to feed you're source (should be named file.pgc BTW) through ecpg
before running cc. That is:

ecpg tryecpg.pgc
cc -o tryecpg tryecpg.c -lecpg -lpq

> What went wrong ?  Please advise.

If this was not the problem we need more details.

> Thanks for giving me the address for the Oracle Pre*C/C++ programmer's guide, it
> is a good reference.  But, it doesn't exactly reflect the ecpg, right?  Is there
> any reference and example program for how to use ecpg?

The reference is pretty outdated but the source comes with three examples.
Oracle's Pro*C manual however is a good reference for the syntac of embedded
SQL, although it does not comply with the standard on some parts.

Michael

- -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

Date: Fri, 12 Feb 1999 06:36:26 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] facing problem with ecpg

> The exec sql should be there after running ecpg. ecpg is a 
> preprocessor. You have to feed you're source (should be named file.pgc 
> BTW) through ecpg before running cc. That is:
>  ecpg tryecpg.pgc
>  cc -o tryecpg tryecpg.c -lecpg -lpq

Michael, could you add a short section with this info to your ecpg sgml
documentation? Also, perhaps you would want to include an example on how
to set up a makefile with a general production rule.

                      - Tom

------------------------------

Date: Fri, 12 Feb 99 9:08:25 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #224

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest  Thursday, February 11 1999  Volume 01 : Number 224



Index:

[none]
Re: [INTERFACES] libpq and multi-threading on Linux?
Troubles with the ODBC driver in the postgres distribution (integrated installation)
Troubles with the ODBC driver in the postgres distribution (integrated installation)
Troubles with the ODBC driver in the postgres distribution (integrated installation)
Troubles with the ODBC driver in the postgres distribution (standalone installation)
ODBC - MSysConf
[none]
pgAdmin v6.4.2
Re: [INTERFACES] facing problem with ecpg
Re: [INTERFACES] ODBC - MSysConf
JDBC: DatabaseMetaData and getPrimaryKeys
Re: [INTERFACES] facing problem with ecpg
Re: [INTERFACES] JDBC: DatabaseMetaData and getPrimaryKeys
Help with ODBC
Help with ODBC in VB6

- ----------------------------------------------------------------------

Date: Thu, 11 Feb 1999 09:42:04 +0200
From: "Sergey T. Soenko" <serg@kzsm.lg.ua>
Subject: [none]

- - -- 
< ++++ÿ+mailto:serg@kzsm.lg.ua

- ------------------------------

Date: Thu, 11 Feb 1999 01:59:37 -0700
From: Brendan Rempel <rempelb@cybersurf.net>
Subject: Re: [INTERFACES] libpq and multi-threading on Linux?

I succeeded in doing exactly that.  I simply took the C source examples on
the Postgres documentation and pasted it into the thread with no problems
at all.  The only changes made to the examples were just simple ones like
return values or fprintf(stderr) stuff, but that's all. Postgres server
and libpq libraries run flawlessly in pthreads.

For me, synchronization was not required since each thread did not share
resources with other threads.  Each thread personally initialized the
libpq connection, did its job and destroyed the connection, just like the
example.

Brendan

Michael Olivier wrote:

> Hi folks,
>
> I apologize in advance if I have overlooked docs, but I haven't been
> able to find a discussion of how PostGreSQL via libpq on Linux fares
> with pthreads. Can someone point me to docs if available, or otherwise
> enlighten me? How well does it work and what are the important design
> issues to consider?
>
> I'm expecting to create a pool of db connections to use within a
> long-running process, which will create a new thread for each incoming
> request from a client. I've found just a very little bit about PG
> being multi-processing, but not how it will interact with a
> multi-threaded client. I appreciate your comments.
>
> thanks,
> --Michael
>
> _________________________________________________________
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com

- ------------------------------

Date: Thu, 11 Feb 1999 10:48:26 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (integrated installation)

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- - -----------------------------------------------
My compilations for integrated installation:



1> integrated installation with a GNU c++
 ./configure --prefix- --with-template- --with-CXX


gmake
...
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
/usr/local/geoscope/src/GNU/package/usr/local/bin/c++  -I../../backend
- - -I../../include -I../../interfaces/libpq -I../../include
- - -I../../backend   -Xa -v -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO
- - -K PIC   -c pgenv.cc -o pgenv.o
c++: cannot specify -o with -c and multiple compilations
gmake[2]: *** [pgenv.o] Error 1
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2



2> integrated installation with /opt/SUNWspro/bin/CC (workshop, solaris)



 ./configure --prefix- --with-template
gmake

gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
CC  -I../../backend -I../../include -I../../interfaces/libpq
- - -I../../include -I../../backend   -Xa -v -D__sparc__ -D__sun__
- - -DDISABLE_COMPLEX_MACRO  -K PIC   -c pgenv.cc -o pgenv.o
CC: Warning: Option -Xa passed to ld, if ld is invoked, ignored
otherwise
CC: Warning: Option -K passed to ld, if ld is invoked, ignored otherwise

### CC: Note: LM_LICENSE_FILE ### CC: Note: NLSPATH /opt/SUNWspro/bin/../SC4.2/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/SUNWspro/bin/../SC4.2/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat

CC: Invalid input file name PIC, no output generated for this file.
/opt/SUNWspro/bin/../SC4.2/bin/ccfe -y-o -ypgenv.o -I../../backend
- - -I../../include -I../../interfaces/libpq -I../../include -I../../backend
- - -y-fbe -y/opt/SUNWspro/bin/../SC4.2/bin/fbe -ptb pgenv.o -y-xarch- -y-verbose -O0 -ptf /tmp/08458%1.%2 -ptx
/opt/SUNWspro/bin/../SC4.2/bin/CC -ptk "-I../../backend -I../../include
- - -I../../interfaces/libpq -I../../include -I../../backend -Xa -v
- - -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO -K -c " -D__SunOS_5_6
- - -D__SUNPRO_CC20 -Dunix -Dsun -Dsparc -D__sparc -D__unix -D__sun
- - -D__BUILTIN_VA_ARG_INCR -D__SVR4 -I/opt/SUNWspro/SC4.2/include/CC
- - -I/opt/SUNWspro/SC4.2/include/CC/rw7 -I/opt/SUNWspro/SC4.2/include/cc
- - -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO pgenv.cc -s
/tmp/ccfe.08458.0.s
"pgenv.h", line 21: Error: Could not open include file <string>.
"pgenv.h", line 25: Error: Type name expected instead of "using".
"pgenv.h", line 48: Error: Type name expected instead of "string".
"pgenv.h", line 48: Error: No storage class or type for this
declaration.
"pgenv.h", line 48: Error: "," expected instead of "pgAuth".
"pgenv.h", line 49: Error: Use ";" to terminate declarations.
"pgenv.h", line 49: Error: Type name expected instead of "string".
"pgenv.h", line 49: Error: No storage class or type for this
declaration.
"pgenv.h", line 49: Error: Multiple declaration for string.
"pgenv.h", line 49: Error: "," expected instead of "pgHost".
"pgenv.h", line 50: Error: Use ";" to terminate declarations.
"pgenv.h", line 50: Error: Type name expected instead of "string".
"pgenv.h", line 50: Error: No storage class or type for this
declaration.
"pgenv.h", line 50: Error: Multiple declaration for string.
"pgenv.h", line 50: Error: "," expected instead of "pgPort".
"pgenv.h", line 51: Error: Use ";" to terminate declarations.
"pgenv.h", line 51: Error: Type name expected instead of "string".
"pgenv.h", line 51: Error: No storage class or type for this
declaration.
"pgenv.h", line 51: Error: Multiple declaration for string.
"pgenv.h", line 51: Error: "," expected instead of "pgOption".
"pgenv.h", line 52: Error: Use ";" to terminate declarations.
"pgenv.h", line 52: Error: Type name expected instead of "string".
"pgenv.h", line 52: Error: No storage class or type for this
declaration.
"pgenv.h", line 52: Error: Multiple declaration for string.
"pgenv.h", line 52: Error: "," expected instead of "pgTty".
Compilation aborted, too many Error messages.
rm /tmp/ccfe.08458.0.s
gmake[2]:







How can I fix the problem?
What is the mistake?

thank you for answering :)



Pascal

- ------------------------------

Date: Thu, 11 Feb 1999 10:57:21 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (integrated installation)

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- - -----------------------------------------------
My compilations for integrated installation:

1> integrated installation with a GNU c++
 ./configure --prefix- --with-template- --with-CXX
gmake
...
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
/usr/local/geoscope/src/GNU/package/usr/local/bin/c++  -I../../backend
- - -I../../include -I../../interfaces/libpq -I../../include
- - -I../../backend   -Xa -v -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO
- - -K PIC   -c pgenv.cc -o pgenv.o
c++: cannot specify -o with -c and multiple compilations
gmake[2]: *** [pgenv.o] Error 1
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2

2> integrated installation with /opt/SUNWspro/bin/CC (workshop, solaris)

 ./configure --prefix- --with-template
gmake

gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
CC  -I../../backend -I../../include -I../../interfaces/libpq
- - -I../../include -I../../backend   -Xa -v -D__sparc__ -D__sun__
- - -DDISABLE_COMPLEX_MACRO  -K PIC   -c pgenv.cc -o pgenv.o
CC: Warning: Option -Xa passed to ld, if ld is invoked, ignored
otherwise
CC: Warning: Option -K passed to ld, if ld is invoked, ignored otherwise

### CC: Note: LM_LICENSE_FILE ### CC: Note: NLSPATH /opt/SUNWspro/bin/../SC4.2/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/SUNWspro/bin/../SC4.2/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat

CC: Invalid input file name PIC, no output generated for this file.
/opt/SUNWspro/bin/../SC4.2/bin/ccfe -y-o -ypgenv.o -I../../backend
- - -I../../include -I../../interfaces/libpq -I../../include -I../../backend
- - -y-fbe -y/opt/SUNWspro/bin/../SC4.2/bin/fbe -ptb pgenv.o -y-xarch- -y-verbose -O0 -ptf /tmp/08458%1.%2 -ptx
/opt/SUNWspro/bin/../SC4.2/bin/CC -ptk "-I../../backend -I../../include
- - -I../../interfaces/libpq -I../../include -I../../backend -Xa -v
- - -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO -K -c " -D__SunOS_5_6
- - -D__SUNPRO_CC20 -Dunix -Dsun -Dsparc -D__sparc -D__unix -D__sun
- - -D__BUILTIN_VA_ARG_INCR -D__SVR4 -I/opt/SUNWspro/SC4.2/include/CC
- - -I/opt/SUNWspro/SC4.2/include/CC/rw7 -I/opt/SUNWspro/SC4.2/include/cc
- - -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO pgenv.cc -s
/tmp/ccfe.08458.0.s
"pgenv.h", line 21: Error: Could not open include file <string>.
"pgenv.h", line 25: Error: Type name expected instead of "using".
"pgenv.h", line 48: Error: Type name expected instead of "string".
"pgenv.h", line 48: Error: No storage class or type for this
declaration.
"pgenv.h", line 48: Error: "," expected instead of "pgAuth".
"pgenv.h", line 49: Error: Use ";" to terminate declarations.
"pgenv.h", line 49: Error: Type name expected instead of "string".
"pgenv.h", line 49: Error: No storage class or type for this
declaration.
"pgenv.h", line 49: Error: Multiple declaration for string.
"pgenv.h", line 49: Error: "," expected instead of "pgHost".
"pgenv.h", line 50: Error: Use ";" to terminate declarations.
"pgenv.h", line 50: Error: Type name expected instead of "string".
"pgenv.h", line 50: Error: No storage class or type for this
declaration.
"pgenv.h", line 50: Error: Multiple declaration for string.
"pgenv.h", line 50: Error: "," expected instead of "pgPort".
"pgenv.h", line 51: Error: Use ";" to terminate declarations.
"pgenv.h", line 51: Error: Type name expected instead of "string".
"pgenv.h", line 51: Error: No storage class or type for this
declaration.
"pgenv.h", line 51: Error: Multiple declaration for string.
"pgenv.h", line 51: Error: "," expected instead of "pgOption".
"pgenv.h", line 52: Error: Use ";" to terminate declarations.
"pgenv.h", line 52: Error: Type name expected instead of "string".
"pgenv.h", line 52: Error: No storage class or type for this
declaration.
"pgenv.h", line 52: Error: Multiple declaration for string.
"pgenv.h", line 52: Error: "," expected instead of "pgTty".
Compilation aborted, too many Error messages.
rm /tmp/ccfe.08458.0.s
gmake[2]:

How can I fix the problem?
What is the mistake?

thank you for answering :)

Pascal

- ------------------------------

Date: Thu, 11 Feb 1999 11:15:14 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (integrated installation)

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- - -----------------------------------------------
My compilations for integrated installation:

1> integrated installation with a GNU c++
 ./configure --prefix- --with-template- --with-CXX
gmake
...
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
/usr/local/geoscope/src/GNU/package/usr/local/bin/c++  -I../../backend
- - -I../../include -I../../interfaces/libpq -I../../include
- - -I../../backend   -Xa -v -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO
- - -K PIC   -c pgenv.cc -o pgenv.o
c++: cannot specify -o with -c and multiple compilations
gmake[2]: *** [pgenv.o] Error 1
gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2

2> integrated installation with /opt/SUNWspro/bin/CC (workshop, solaris)

 ./configure --prefix- --with-template
gmake

gmake[2]: Leaving directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/ecpg'
gmake -C libpq++ all
gmake[2]: Entering directory
`/usr/localsgbd1/postgresql-6.4.2/src/interfaces/libpq++'
CC  -I../../backend -I../../include -I../../interfaces/libpq
- - -I../../include -I../../backend   -Xa -v -D__sparc__ -D__sun__
- - -DDISABLE_COMPLEX_MACRO  -K PIC   -c pgenv.cc -o pgenv.o
CC: Warning: Option -Xa passed to ld, if ld is invoked, ignored
otherwise
CC: Warning: Option -K passed to ld, if ld is invoked, ignored otherwise

### CC: Note: LM_LICENSE_FILE ### CC: Note: NLSPATH /opt/SUNWspro/bin/../SC4.2/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/SUNWspro/bin/../SC4.2/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat

CC: Invalid input file name PIC, no output generated for this file.
/opt/SUNWspro/bin/../SC4.2/bin/ccfe -y-o -ypgenv.o -I../../backend
- - -I../../include -I../../interfaces/libpq -I../../include -I../../backend
- - -y-fbe -y/opt/SUNWspro/bin/../SC4.2/bin/fbe -ptb pgenv.o -y-xarch- -y-verbose -O0 -ptf /tmp/08458%1.%2 -ptx
/opt/SUNWspro/bin/../SC4.2/bin/CC -ptk "-I../../backend -I../../include
- - -I../../interfaces/libpq -I../../include -I../../backend -Xa -v
- - -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO -K -c " -D__SunOS_5_6
- - -D__SUNPRO_CC20 -Dunix -Dsun -Dsparc -D__sparc -D__unix -D__sun
- - -D__BUILTIN_VA_ARG_INCR -D__SVR4 -I/opt/SUNWspro/SC4.2/include/CC
- - -I/opt/SUNWspro/SC4.2/include/CC/rw7 -I/opt/SUNWspro/SC4.2/include/cc
- - -D__sparc__ -D__sun__ -DDISABLE_COMPLEX_MACRO pgenv.cc -s
/tmp/ccfe.08458.0.s
"pgenv.h", line 21: Error: Could not open include file <string>.
"pgenv.h", line 25: Error: Type name expected instead of "using".
"pgenv.h", line 48: Error: Type name expected instead of "string".
"pgenv.h", line 48: Error: No storage class or type for this
declaration.
"pgenv.h", line 48: Error: "," expected instead of "pgAuth".
"pgenv.h", line 49: Error: Use ";" to terminate declarations.
"pgenv.h", line 49: Error: Type name expected instead of "string".
"pgenv.h", line 49: Error: No storage class or type for this
declaration.
"pgenv.h", line 49: Error: Multiple declaration for string.
"pgenv.h", line 49: Error: "," expected instead of "pgHost".
"pgenv.h", line 50: Error: Use ";" to terminate declarations.
"pgenv.h", line 50: Error: Type name expected instead of "string".
"pgenv.h", line 50: Error: No storage class or type for this
declaration.
"pgenv.h", line 50: Error: Multiple declaration for string.
"pgenv.h", line 50: Error: "," expected instead of "pgPort".
"pgenv.h", line 51: Error: Use ";" to terminate declarations.
"pgenv.h", line 51: Error: Type name expected instead of "string".
"pgenv.h", line 51: Error: No storage class or type for this
declaration.
"pgenv.h", line 51: Error: Multiple declaration for string.
"pgenv.h", line 51: Error: "," expected instead of "pgOption".
"pgenv.h", line 52: Error: Use ";" to terminate declarations.
"pgenv.h", line 52: Error: Type name expected instead of "string".
"pgenv.h", line 52: Error: No storage class or type for this
declaration.
"pgenv.h", line 52: Error: Multiple declaration for string.
"pgenv.h", line 52: Error: "," expected instead of "pgTty".
Compilation aborted, too many Error messages.
rm /tmp/ccfe.08458.0.s
gmake[2]:

How can I fix the problem?
What is the mistake?

thank you for answering :)

Pascal

- ------------------------------

Date: Thu, 11 Feb 1999 12:06:34 +0100
From: Pascal DAYRE <dayre@ipgp.jussieu.fr>
Subject: Troubles with the ODBC driver in the postgres distribution (standalone installation)

- - --------------668455E0634BA07049CA63EA
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit

(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

Hello everybody, can you help me?

I 've tried to install the ODBC driver like the description
in "PostgreSQL Programmer's Guide" guide (153-157).
I've tried the integrated installation and also the standalone
installation.

What is the compiler needed for C++? I have tried a GNU one and a
Solaris one?
What is the good version for GNU C++?

- - -----------------------------------------------
My compilations for standalone installation:

1> standalone installation with a GNU c++


cd interfaces/odbc

gmake standalone

rm -f psqlodbc-025.tar.gz
/bin/tar -chf psqlodbc-025.tar \
    *.c *.h *.in Config.mk TODO.txt Version.mk config.guess config.sub
configure install-sh license.txt notice.txt odbcinst.ini psqlodbc.def
psqlodbc.rc readme.txt -C ../.. makefiles template Makefile.shlib
tar: Makefile.shlib: No such file or directory
gmake: *** [standalone] Error 1
[root@geosp15]tcsh(14)





How can I fix the problem?
What is the mistake?

thank you for answering :)

Pascal




- - --

- - -------------------------------------------
        Pascal  DAYRE

        dayre@ipgp.jussieu.fr
        tel:    (33) 1 44 27 38 96
        fax:    (33) 1 44 27 38 94
- - --------------------------------------------



- - --------------668455E0634BA07049CA63EA
Content-Type: text/html; charsetContent-Transfer-Encoding: 7bit

<HTML>
(Sparc Ultra10, solaris 2.6, Postgres 6.4.2)

<P>Hello everybody, can you help me?

<P>I 've tried to install the ODBC driver like the description
<BR>in "PostgreSQL Programmer's Guide" guide (153-157).
<BR>I've tried the integrated installation and also the standalone
<BR>installation.

<P>What is the compiler needed for C++? I have tried a GNU one and a
<BR>Solaris one?
<BR>What is the good version for GNU C++?

<P>-----------------------------------------------
<BR>My compilations for standalone installation:

<P>1> standalone installation with a GNU c++
<BR>&nbsp;

<P>cd interfaces/odbc

<P>gmake standalone

<P>rm -f psqlodbc-025.tar.gz
<BR>/bin/tar -chf psqlodbc-025.tar \
<BR>&nbsp;&nbsp;&nbsp; *.c *.h *.in Config.mk TODO.txt Version.mk config.guess
config.sub configure install-sh license.txt notice.txt odbcinst.ini psqlodbc.def
psqlodbc.rc readme.txt -C ../.. makefiles template Makefile.shlib
<BR>tar: Makefile.shlib: No such file or directory
<BR>gmake: *** [standalone] Error 1
<BR>[root@geosp15]tcsh(14)
<BR>&nbsp;
<BR>&nbsp;
<BR>&nbsp;
<BR>&nbsp;

<P>How can I fix the problem?
<BR>What is the mistake?

<P>thank you for answering :)

<P>Pascal
<BR>&nbsp;
<BR>&nbsp;
<BR>&nbsp;
<PRE>--&nbsp;


- - -------------------------------------------
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pascal&nbsp; DAYRE

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dayre@ipgp.jussieu.fr
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tel:&nbsp;&nbsp;&nbsp; (33) 1 44 27 38 96
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fax:&nbsp;&nbsp;&nbsp; (33) 1 44 27 38 94
- - --------------------------------------------</PRE>
&nbsp;</HTML>

- - --------------668455E0634BA07049CA63EA--

- ------------------------------

Date: Thu, 11 Feb 1999 12:59:49 -0800
From: Karsten Kaus <kk@kdschmid.de>
Subject: ODBC - MSysConf

ok, in general it seems to be possible to connect Access97 ( not Access
2.0! ?right?  ) to postgres.
It works on ONE of my Computers in the office (486). On that computer
I cannot start the 32Bit-ODBC in the systemconfiguration, but I can
create DSNs within Access97, and I get connected to any postgres-
database I wish (tried only 2).
On my Pentium in the office and on ALL machines at home I get the 
error 4307, that there is a Table called MSysConf on my server but
it does not have the expected format.
I searched for this table using grep and pg_dumpall as well as psql \dS
and could not find anything. So I created one as described in the
MSAccess-Help, but this didn't help. Still the fomat was invalid.
I do not want to use this table anyway ( do I? ), so what to do?

Thanks for help,
Karsten Kaus

- ------------------------------

Date: Thu, 11 Feb 1999 14:09:24 +0100
From: Andreas Kaschke <kaschke@books.de>
Subject: [none]

subscribe

- ------------------------------

Date: Thu, 11 Feb 1999 16:06:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: pgAdmin v6.4.2

I've just released pgAdmin v6.4.2 which is available from:

http://www.vale-it.demon.co.uk/freeware

New features/enhancements include:

1) Improved the error logging to include details of the database connection
and some internal variables in the logfile.
2) Added a check to prevent use with earlier  versions of PostgreSQL than
are compatible.
3) Added checks to warn the user if the ODBC driver settings for the
datasource could cause problems with the operation of pgAdmin.
4) Added a Database browser dialogue with Create and Drop database
facilities.

Please note that pgAdmin 6.4.x will only work correctly with PostgreSQL
6.4.x.

Regards,

Dave.
- - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!

- ------------------------------

Date: Fri, 12 Feb 1999 00:42:34 +0800
From: hoelc <hoelc@pd.jaring.my>
Subject: Re: [INTERFACES] facing problem with ecpg

Hello,
I've just upgrated my PostgreSQL system to version Postgres-6.4.2
Now it has the *ecpg
But I'm facing problem in using it, when I compile the C program with
        cc -o tryecpg tryecpg.c -lecpg -lpq
the compiler can't recognize the " exec sql ", and give error massage
       Parse error before 'sql'

What went wrong ?  Please advise.
Thanks for giving me the address for the Oracle Pre*C/C++ programmer's guide, it
is a good reference.  But, it doesn't exactly reflect the ecpg, right?  Is there
any reference and example program for how to use ecpg?
Thank you very much.

Regards,
LCH

Michael Meskes wrote:

> On Sat, Feb 06, 1999 at 07:16:14PM -0600, James Thompson wrote:
> > http://www.dal.ca/%7eoracle/oradoc/DOC/api/doc/PC_22/toc.htm
>
> Gotta look at this.
>
> > With it you end up with something like the following in your code
> >
> >     exec sql
> >       insert into customer(id,name_first,name_middle,name_last,company,
> >                       address1,address2,city,state,country,zip,phone_work,
> >                       phone_home,phone_fax,email,date_entered,billing_terms,
> >                            confirmation_method)
> >       values (:id,:name_first, :name_middle, :name_last,
> >               :company,:address1,:address2,
> >               :city,:state,:country,:zip,:phone_work,
> >               :phone_home,:phone_fax,:email,date('now'),
> >               :billing_terms,
> >               :confirmation_method);
>
> Xou can even add indicators like in
>
> ... values (:id,:name_first, :name_middle:nm_ind, :name_last, ...
>
> If nm_ind is set to -1 the name_middle entry will be set to NULL.
>
> > The author of the code is very responsive to few problem reports I have
> > sent him and has sent patches, or workarounds to me usually within 24
> > hours.
>
> Glad I can help. :-)
>
> > In the few cases you can't figure out a way to make something happen using
> > ecpg I believe you can mix the libpg and ecpg code in the same program.
> > The only place I could see a need for this is when you'd need the
> > functionality given by Pro*C's Dynamic SQL which ecpg doesn't yet support,
> > but I think its in the works.
>
> It is. In fact I already submitted a patch for the PREPARE and EXECUTE
> commands. James, if you'd like to test this I can send you the source until
> it makes its way into CVS.
>
> Michael
> --
> Michael Meskes                         | Go SF 49ers!
> Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
> Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
> Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

Date: Thu, 11 Feb 1999 09:35:12 -0500
From: David Hartwig <daveh@insightdist.com>
Subject: Re: [INTERFACES] ODBC - MSysConf

Karsten Kaus wrote:

> ok, in general it seems to be possible to connect Access97 ( not Access
> 2.0! ?right?  ) to postgres.

I recall someone doing this successfully.  The key here is that it needs to
be running on Win95, Win98, or NT.

>
> It works on ONE of my Computers in the office (486). On that computer
> I cannot start the 32Bit-ODBC in the systemconfiguration, but I can
> create DSNs within Access97, and I get connected to any postgres-
> database I wish (tried only 2).
> On my Pentium in the office and on ALL machines at home I get the
> error 4307, that there is a Table called MSysConf on my server but
> it does not have the expected format.

You do not need this table on the server.  The driver will report it as an
error in the log file, but it should not be a problem to the application.

Activate the CommLog in the driver settings and send a copy of the errant
session.  Its located in C:\psqlodbc*.log.

>
> I searched for this table using grep and pg_dumpall as well as psql \dS
> and could not find anything. So I created one as described in the
> MSAccess-Help, but this didn't help. Still the fomat was invalid.
> I do not want to use this table anyway ( do I? ), so what to do?
>

I would drop the table unless you know what you are doing with MSysConf. At
least until you get on solid footing.   It's improper configuration may
cause other problems.

- ------------------------------

Date: Thu, 11 Feb 1999 20:36:06 +0100
From: "Alejandro Alberola Arias" <alberola@bio.es>
Subject: JDBC: DatabaseMetaData and getPrimaryKeys

Hi,

I am using PostgreSQL 6.4 on a Linux box and its JDBC driver.

The problem is that the getPrimaryKeys() method of the
DatabaseMetaData class doesn't work for me. 

Any ideas ?

Thanks.

Alejandro Alberola
alberola@bio.es

- ------------------------------

Date: Thu, 11 Feb 1999 20:51:42 +0100
From: Michael Meskes <Michael.Meskes@gmx.net>
Subject: Re: [INTERFACES] facing problem with ecpg

On Fri, Feb 12, 1999 at 12:42:34AM +0800, hoelc wrote:
> Hello,
> I've just upgrated my PostgreSQL system to version Postgres-6.4.2
> Now it has the *ecpg
> But I'm facing problem in using it, when I compile the C program with
>         cc -o tryecpg tryecpg.c -lecpg -lpq
> the compiler can't recognize the " exec sql ", and give error massage
>        Parse error before 'sql'

The exec sql should be there after running ecpg. ecpg is a preprocessor. You
have to feed you're source (should be named file.pgc BTW) through ecpg
before running cc. That is:

ecpg tryecpg.pgc
cc -o tryecpg tryecpg.c -lecpg -lpq

> What went wrong ?  Please advise.

If this was not the problem we need more details.

> Thanks for giving me the address for the Oracle Pre*C/C++ programmer's guide, it
> is a good reference.  But, it doesn't exactly reflect the ecpg, right?  Is there
> any reference and example program for how to use ecpg?

The reference is pretty outdated but the source comes with three examples.
Oracle's Pro*C manual however is a good reference for the syntac of embedded
SQL, although it does not comply with the standard on some parts.

Michael
- - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

Date: Thu, 11 Feb 1999 14:31:15 -0600
From: "John Barrett" <jbarrett@onramp.net>
Subject: Re: [INTERFACES] JDBC: DatabaseMetaData and getPrimaryKeys

This is a multi-part message in MIME format.

- - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

I've attached a quick and dirty little application in Java I use to transfer
data from one server to another
It uses the getPrimaryKeys call and works nicely... please excuse the lack
of documentation/comments :)))))

Might help ya to see a working app that uses the method.....

- - -----Original Message-----
From: Alejandro Alberola Arias <alberola@bio.es>
To: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Date: Thursday, February 11, 1999 1:39 PM
Subject: [INTERFACES] JDBC: DatabaseMetaData and getPrimaryKeys


>Hi,
>
>I am using PostgreSQL 6.4 on a Linux box and its JDBC driver.
>
>The problem is that the getPrimaryKeys() method of the
>DatabaseMetaData class doesn't work for me.
>
>Any ideas ?
>
>Thanks.
>
>Alejandro Alberola
>alberola@bio.es
>
>
>
>

- - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
import java.sql.*;
import java.util.Vector;

class DBLogin
{
	public	String	username;
	public	String	password;
	public	String	connurl;
	
	public DBLogin(String u, String p, String c)
	{
		username 		password 		connurl 	}
}

class DBField
{
	public	int	fnum;
	public	int	ftyp;
	public	int	fsiz;
	public	int	fdig;
	public	String	fnam;
	public	String	fdef;
	
	public DBField(ResultSet res) throws SQLException
	{
		fnum 		ftyp 		fsiz 		fdig 		ftyp 		fnam 		fdef 	
		if (fdef.equals("VARCHAR2")) {
			fdef 		}
		
		if (fdef.equals("DATE")) {
			fdef 		}
		
		if (fdef.equals("VARCHAR")) {
			fdef 		}
		if (fdef.equals("NUMBER")) {
			if (fdig 				// integer
				fdef 			} else {
				if (fdig 					fdef 				} else {
					fdef 				}
			}
		}
		fdef 	}
	
	public String toString()
	{
		return fnam + " " + fdef;
	}
}
			
class DBXfer
{
	Connection	srcConn;
	Connection	dstConn;
	DBLogin		srcLogin;
	DBLogin		dstLogin;

	public static void main(String argv[])
	{
		try {
			Class.forName ("oracle.jdbc.driver.OracleDriver");
			DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
	
			Class.forName ("postgresql.Driver");
			DriverManager.registerDriver (new postgresql.Driver());
		} catch (Exception e) {
			System.out.println("Cound Not Register Drivers");
			return;
		}

		DBLogin	srcLogin 		DBLogin	dstLogin 		DBXfer dbx 		
		dbx.transfer(null,"schema","table");
	}
	
	public DBXfer(DBLogin src, DBLogin dst)
	{
		srcLogin 		dstLogin 		
		try {
			srcConn 		} catch (Exception e) {
			System.out.println("Could not open source connection: " + e);
			return;
		}
		try {
			dstConn 		} catch (Exception e) {
			System.out.println("Could not open destination connection: " + e);
			srcConn 			return;
		}
	}

	public void transfer(String catalog, String schema, String table)
	{
		ResultSet	res;
		String		srcsql;
		String		dstsql;
		String		pkey[];
		int		pmax;
		DBField		fdat[];
		int		fmax;
		int		i;
		String		com;

		srcsql 		dstsql 		com 		pmax 		pkey 		fmax 		fdat 
		try {
			DatabaseMetaData dmd 			
			res 			while (res.next()) {
				DBField	tmp 				fdat[tmp.fnum] 				if (tmp.fnum > fmax) {
					fmax 				}
			}
			
			for (imax+1;i++) {
				srcsql 				dstsql 				com 			}

			res 			while (res.next()) {
				//System.out.println("Primary("+res.getString(5)+"): " + res.getString(4));
				pkey[res.getInt(5)] 				if (res.getInt(5) > pmax) {
					pmax 				}
			}
			if (pmax > 0) { // got a primary key
				srcsql 				com 				for (ix+1;i++) {
					srcsql 					com 				}
				srcsql 			}

			srcsql 			System.out.println(srcsql);
			
			// finish building destination insert statement
			dstsql 			com 			for (imax+1;i++) {
				dstsql 				com 			}
			dstsql 			System.out.println(dstsql);
						
			// we got everything we need.... lets do something with it !!
			Statement dstcmd 			
			// drop the table if it exists
			try {
				dstcmd.executeUpdate("drop table " + table);
			} catch (Exception e) {}
			
			// create table using the definition we just assembled
			System.out.println("creating table");
			System.out.flush();
			dstcmd.executeUpdate(srcsql);
			
			// we got a table.... get the data
			Statement srccmd 			System.out.println("accessing source data");
			System.out.flush();
			res 			
			// setup to store data to new table
			System.out.println("building insert statement");
			System.out.flush();
			PreparedStatement dstins 			
			// move that data !!
			int cnt 			String fld;
			while (res.next()) {
				System.out.println("				System.out.flush();
				for (imax+1;i++) {
					fld 					if (fld 						System.out.println(i + "\t" + fdat[i].ftyp + "\t" + fdat[i].fdig + "\t" + null);
					} else {
						System.out.println(i + "\t" + fdat[i].ftyp + "\t" + fdat[i].fdig + "\t" + fld.toString());
					}
					System.out.flush();
					if (fld 						dstins.setNull(i,fdat[i].ftyp);
					} else {
						dstins.setString(i,fld);
					}
				}
				dstins.executeUpdate();
			}
			
		} catch (Exception e) {
			System.out.println("Exception: " + e);
		}
	}
}
- - ------
- ------------------------------

Date: Thu, 11 Feb 1999 17:59:29 -0500
From: "Stephen Turner" <stephen@edtechnews.com>
Subject: Help with ODBC

This is a multi-part message in MIME format.

- - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: quoted-printable

subscribe me


I have Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect through the internet with ODBC. I'm currently working on a project with Visual Basic where I can connect to Postgres and edit the database. I did edit the pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight and I notice in the configuration help that it refered to something else besides the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is how do I know when I'm connected through ODBC because I can't tell.

Thanks in advance

Stephen Turner
stephen@edtechnews.com

- - ------Content-Type: text/html;
	charsetContent-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content<META content</HEAD>
<BODY bgColor<DIV><FONT size+scribe me</FONT></DIV>
<DIV><FONT size/ONT>&nbsp;</DIV>
<DIV><FONT size/ONT>&nbsp;</DIV>
<DIV><FONT size*ve Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect 
through the internet with ODBC. I'm currently working on a project with Visual 
Basic where I can connect to Postgres and edit the database. I did edit the 
pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight 
and I notice in the configuration help that it refered to something else besides 
the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is 
how do I know when I'm connected through ODBC because I can't tell.</FONT></DIV>
<DIV><FONT size/ONT>&nbsp;</DIV>
<DIV><FONT size*nks in advance</FONT></DIV>
<DIV><FONT size/ONT>&nbsp;</DIV>
<DIV><FONT size.phen Turner</FONT></DIV>
<DIV><FONT size* 
href
- - ------
- ------------------------------

Date: Thu, 11 Feb 1999 18:04:00 -0500
From: "Stephen Turner" <stephen@edtechnews.com>
Subject: Help with ODBC in VB6

This is a multi-part message in MIME format.

- - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: quoted-printable

subscribe

I have Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect through the internet with ODBC. I'm currently working on a project with Visual Basic where I can connect to Postgres and edit the database. I did edit the pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight and I notice in the configuration help that it refered to something else besides the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is how do I know when I'm connected through ODBC because I can't tell.
 
Thanks in advance
 
Stephen Turner
stephen@edtechnews.com

- - ------Content-Type: text/html;
	charsetContent-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content<META content</HEAD>
<BODY bgColor<DIV>
<DIV><FONT size/ONT><FONT color<DIV><FONT size/ONT>&nbsp;</DIV>
<DIV><FONT size*ve Red Hat 5.2 with PostgreSQL 6.3.2 and I want to connect 
through the internet with ODBC. I'm currently working on a project with Visual 
Basic where I can connect to Postgres and edit the database. I did edit the 
pg_hba.conf but that didn't seem to help. I downloaded the driver from Insight 
and I notice in the configuration help that it refered to something else besides 
the 32bit ODBC applet in the Control Panel folder. I guess what I'm asking is 
how do I know when I'm connected through ODBC because I can't tell.</FONT></DIV>
<DIV><FONT size/ONT>&nbsp;</DIV>
<DIV><FONT size*nks in advance</FONT></DIV>
<DIV><FONT size/ONT>&nbsp;</DIV>
<DIV><FONT size.phen Turner</FONT></DIV>
<DIV><FONT size* 
href
- - ------
- ------------------------------

End of pgsql-interfaces-digest V1 #224
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #226
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-02 22:25 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-02 22:25 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- --
- -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- -------------------------------------------------------------------

------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- -	if I open the form on an exising record, it works great

- -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn=153237224, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='1',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153237224, query=' '
conn=153237224, query='set DateStyle to 'ISO''
conn=153237224, query='set geqo to 'OFF''
conn=153237224, query='set ksqo to 'ON''
conn=153237224, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153237224, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153237224, query='SELECT Config, nValue FROM MSysConf'
ERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
                 - ------------------------------------------------------------
                 hdbc=153237224, stmt=153550944, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=0, parameters_allocated=0
                 statement_type=0, statement='SELECT Config, nValue FROM MSysConf'
                 stmt_with_params='SELECT Config, nValue FROM MSysConf'
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR09270060'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR:  msysconf: Table does not exist.'
            - ------------------------------------------------------------
            henv=153237168, conn=153237224, status=1, num_stmts=16
            sock=153243592, stmts=153251960, lobj_type=-999
            ---------------- Socket Info - -------------------------------
            socket=324, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=153243672, buffer_out=153247816
            buffer_filled_in=42, buffer_filled_out=0, buffer_read_in=42
conn=153237224, query='SELECT "rentalorders"."rentalorderid" FROM "rentalorders" '
    [ fetched 920 rows ]
conn=153632808, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='1',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153632808, query=' '
conn=153632808, query='set DateStyle to 'ISO''
conn=153632808, query='set geqo to 'OFF''
conn=153632808, query='set ksqo to 'ON''
conn=153632808, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153632808, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153632808, query='SELECT "rentalorderid","memberid","processedby","dateprocessed","shippedby","dateshipped","returnedby","shippinghandling","shownotes","notes","batchno"  FROM "rentalorders"  WHERE "rentalorderid" = 1'
    [ fetched 1 rows ]
conn=153723168, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='1',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153723168, query=' '
conn=153723168, query='set DateStyle to 'ISO''
conn=153723168, query='set geqo to 'OFF''
conn=153723168, query='set ksqo to 'ON''
conn=153723168, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153723168, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153723168, query='SELECT "RentalOrders"."rentalorderlinesid" FROM "rentalorderlines" "RentalOrders" WHERE ("rentalorderid" =  1 ) '
    [ fetched 10 rows ]
conn=153723168, SQLDisconnect
conn=153632808, query='SELECT "rentalorderlinesid","rentalorderid","rentalid","quantity","cost","notinstock","nolongeravailable","returned","returneddate"  FROM "rentalorderlines"  WHERE "rentalorderlinesid" = 1 OR "rentalorderlinesid" = 2 OR "rentalorderlinesid" = 3 OR "rentalorderlinesid" = 4 OR "rentalorderlinesid" = 5 OR "rentalorderlinesid" = 6 OR "rentalorderlinesid" = 7 OR "rentalorderlinesid" = 8 OR "rentalorderlinesid" = 9 OR "rentalorderlinesid" = 10'
    [ fetched 10 rows ]
conn=153802280, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153802280, query=' '
conn=153802280, query='set DateStyle to 'ISO''
conn=153802280, query='set geqo to 'OFF''
conn=153802280, query='set ksqo to 'ON''
conn=153802280, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153802280, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153812792, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153812792, query=' '
conn=153812792, query='set DateStyle to 'ISO''
conn=153812792, query='set geqo to 'OFF''
conn=153812792, query='set ksqo to 'ON''
conn=153812792, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153812792, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153812792, query='SELECT "inventoryid" ,"inventoryname" ,"tapenum"  FROM "inventory" ORDER BY "inventoryid"  '
    [ fetched 570 rows ]
conn=153802280, query='SELECT "rentalid" ,"inventoryid" ,"obsolete"  FROM "rentals" ORDER BY "inventoryid"  '
    [ fetched 163 rows ]
conn=153812792, SQLDisconnect
conn=153802280, SQLDisconnect
conn=153944104, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153944104, query=' '
conn=153944104, query='set DateStyle to 'ISO''
conn=153944104, query='set geqo to 'OFF''
conn=153944104, query='set ksqo to 'ON''
conn=153944104, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153944104, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153944104, query='SELECT "logvalues"."id" FROM "logvalues" '
ERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
                 - ------------------------------------------------------------
                 hdbc=153944104, stmt=153950776, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=0, parameters_allocated=0
                 statement_type=0, statement='SELECT "logvalues"."id" FROM "logvalues" '
                 stmt_with_params='SELECT "logvalues"."id" FROM "logvalues" '
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR092D1A38'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR:  logvalues: Permission denied.'
            ------------------------------------------------------------
            henv=153237168, conn=153944104, status=1, num_stmts=16
            sock=153797296, stmts=153646224, lobj_type=-999
            ---------------- Socket Info - -------------------------------
            socket=356, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=153791272, buffer_out=153898984
            buffer_filled_in=40, buffer_filled_out=0, buffer_read_in=40
conn=153944104, SQLDisconnect
conn=153944104, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153944104, query=' '
conn=153944104, query='set DateStyle to 'ISO''
conn=153944104, query='set geqo to 'OFF''
conn=153944104, query='set ksqo to 'ON''
conn=153944104, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153944104, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153944104, query='SELECT "memberid" ,"firstname" ,"lastname"  FROM "membership" ORDER BY "lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
                 - ------------------------------------------------------------
                 hdbc=153944104, stmt=153950776, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=0, parameters_allocated=0
                 statement_type=0, statement='SELECT "memberid" ,"firstname" ,"lastname"  FROM "membership" ORDER BY "lastname" ,"firstname"  '
                 stmt_with_params='SELECT "memberid" ,"firstname" ,"lastname"  FROM "membership" ORDER BY "lastname" ,"firstname"  '
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR092D1A38'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR:  membership: Permission denied.'
            - ------------------------------------------------------------
            henv=153237168, conn=153944104, status=1, num_stmts=16
            sock=153797296, stmts=153646224, lobj_type=-999
            ---------------- Socket Info - -------------------------------
            socket=384, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=153791272, buffer_out=153898984
            buffer_filled_in=41, buffer_filled_out=0, buffer_read_in=41
conn=153944104, SQLDisconnect
conn=153632808, query='SELECT "rentalorderid","memberid","processedby","dateprocessed","shippedby","dateshipped","returnedby","shippinghandling","shownotes","notes","batchno"  FROM "rentalorders"  WHERE "rentalorderid" = 1'
    [ fetched 1 rows ]
conn=153944104, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153944104, query=' '
conn=153944104, query='set DateStyle to 'ISO''
conn=153944104, query='set geqo to 'OFF''
conn=153944104, query='set ksqo to 'ON''
conn=153944104, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153944104, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153944104, query='SELECT "memberid" ,"firstname" ,"middleinitial" ,"lastname" ,"surname" ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected" ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname" ,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
                 - ------------------------------------------------------------
                 hdbc=153944104, stmt=153950776, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=0, parameters_allocated=0
                 statement_type=0, statement='SELECT "memberid" ,"firstname" ,"middleinitial" ,"lastname" ,"surname" ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected" ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname" ,"recordtype"  FROM "membership" '
                 stmt_with_params='SELECT "memberid" ,"firstname" ,"middleinitial" ,"lastname" ,"surname" ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected" ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname" ,"recordtype"  FROM "membership" '
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR092D1A38'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR:  membership: Permission denied.'
            - ------------------------------------------------------------
            henv=153237168, conn=153944104, status=1, num_stmts=16
            sock=153797296, stmts=153646224, lobj_type=-999
            ---------------- Socket Info - -------------------------------
            socket=428, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=153791272, buffer_out=153890856
            buffer_filled_in=41, buffer_filled_out=0, buffer_read_in=41
conn=153944104, SQLDisconnect
conn=153944104, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153944104, query=' '
conn=153944104, query='set DateStyle to 'ISO''
conn=153944104, query='set geqo to 'OFF''
conn=153944104, query='set ksqo to 'ON''
conn=153944104, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153944104, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153944104, query='SELECT "membership"."memberid" ,"membership"."firstname" ,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership" WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" = "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
                 - ------------------------------------------------------------
                 hdbc=153944104, stmt=153950776, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=0, parameters_allocated=0
                 statement_type=0, statement='SELECT "membership"."memberid" ,"membership"."firstname" ,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership" WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" = "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
                 stmt_with_params='SELECT "membership"."memberid" ,"membership"."firstname" ,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership" WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" = "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR092D1A38'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR:  memberservices: Permission denied.'
            - ------------------------------------------------------------
            henv=153237168, conn=153944104, status=1, num_stmts=16
            sock=153797296, stmts=153646224, lobj_type=-999
            ---------------- Socket Info - -------------------------------
            socket=348, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=153890856, buffer_out=153791272
            buffer_filled_in=45, buffer_filled_out=0, buffer_read_in=45
conn=153944104, SQLDisconnect
conn=153944104, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153944104, query=' '
conn=153944104, query='set DateStyle to 'ISO''
conn=153944104, query='set geqo to 'OFF''
conn=153944104, query='set ksqo to 'ON''
conn=153944104, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153944104, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153944104, query='SELECT "memberid" ,"firstname" ,"middleinitial" ,"lastname" ,"surname" ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected" ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname" ,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
                 - ------------------------------------------------------------
                 hdbc=153944104, stmt=153950776, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=0, parameters_allocated=0
                 statement_type=0, statement='SELECT "memberid" ,"firstname" ,"middleinitial" ,"lastname" ,"surname" ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected" ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname" ,"recordtype"  FROM "membership" '
                 stmt_with_params='SELECT "memberid" ,"firstname" ,"middleinitial" ,"lastname" ,"surname" ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected" ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname" ,"recordtype"  FROM "membership" '
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR092D1A38'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR:  membership: Permission denied.'
            - ------------------------------------------------------------
            henv=153237168, conn=153944104, status=1, num_stmts=16
            sock=153797296, stmts=153646224, lobj_type=-999
            ---------------- Socket Info - -------------------------------
            socket=428, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=153890856, buffer_out=153791272
            buffer_filled_in=41, buffer_filled_out=0, buffer_read_in=41
conn=153944104, SQLDisconnect
conn=153237224, query='SELECT "RentalOrders"."rentalorderlinesid" FROM "rentalorderlines" "RentalOrders" WHERE ("rentalorderid" =  NULL ) '
ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while executing the query'
                 - ------------------------------------------------------------
                 hdbc=153237224, stmt=153550944, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=153645616, parameters_allocated=1
                 statement_type=0, statement='SELECT "RentalOrders"."rentalorderlinesid" FROM "rentalorderlines" "RentalOrders" WHERE ("rentalorderid" =  ? ) '
                 stmt_with_params='SELECT "RentalOrders"."rentalorderlinesid" FROM "rentalorderlines" "RentalOrders" WHERE ("rentalorderid" =  NULL ) '
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR09270060'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR:  parser: parse error at or near "null"'
            - ------------------------------------------------------------
            henv=153237168, conn=153237224, status=1, num_stmts=16
            sock=153243592, stmts=153251960, lobj_type=-999
            ---------------- Socket Info - -------------------------------
            socket=324, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=153243672, buffer_out=153247816
            buffer_filled_in=48, buffer_filled_out=0, buffer_read_in=48
conn=153944104, SQLDriverConnect( in)='DSN=PostgreSQL;UID=Admin;PWD=;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS=;', fDriverCompletion=0
DSN info: DSN='PostgreSQL',server='192.168.97.2',port='5432',dbase='mp',user='Admin',passwd=''
          readonly='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='1'
          conn_settings=''
          translation_dll='',translation_option=''
Global Options: Version='06.40.0004', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=153944104, query=' '
conn=153944104, query='set DateStyle to 'ISO''
conn=153944104, query='set geqo to 'OFF''
conn=153944104, query='set ksqo to 'ON''
conn=153944104, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
conn=153944104, SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='
conn=153944104, query='SELECT "inventoryid" ,"inventoryname" ,"tapenum"  FROM "inventory" ORDER BY "inventoryid"  '
    [ fetched 570 rows ]
conn=153237224, query='SELECT "rentalid" ,"inventoryid" ,"obsolete"  FROM "rentals" ORDER BY "inventoryid"  '
    [ fetched 163 rows ]
conn=153944104, SQLDisconnect
conn=153632808, query='SELECT "rentalorderid","memberid","processedby","dateprocessed","shippedby","dateshipped","returnedby","shippinghandling","shownotes","notes","batchno"  FROM "rentalorders"  WHERE "rentalorderid" = 847 OR "rentalorderid" = 848 OR "rentalorderid" = 849 OR "rentalorderid" = 850 OR "rentalorderid" = 851 OR "rentalorderid" = 852 OR "rentalorderid" = 853 OR "rentalorderid" = 854 OR "rentalorderid" = 855 OR "rentalorderid" = 856'
    [ fetched 10 rows ]
conn=153632808, SQLDisconnect
conn=153237224, SQLDisconnect

- ------_
------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-02 23:10 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-02 23:10 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - --
- - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - -------------------------------------------------------------------

- ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - -	if I open the form on an exising record, it works great

- - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - ------_
- ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 02:12 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 02:12 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid­min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - --
- - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - -------------------------------------------------------------------

- - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - -	if I open the form on an exising record, it works great

- - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - ------_
- - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid­min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID­min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 03:19 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 03:19 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid¡min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - --
- - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - -------------------------------------------------------------------

- - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - -	if I open the form on an exising record, it works great

- - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - ------_
- - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid¡min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID¡min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 04:09 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 04:09 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uidímin.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - --
- - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - -------------------------------------------------------------------

- - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - -	if I open the form on an exising record, it works great

- - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - ------_
- - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uidímin.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UIDímin;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 04:34 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 04:34 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #251

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 251



Index:

postdrv ODBC driver problems

----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter@alef.gcsu.edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved.  Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem.  Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query.  It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess.  Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now.  I can't get to the machines
I use Windows on until tomorrow.  It shouldn't be too difficult to
recreate the error if you want to look into it.  Just try to access a
table that uses mixed case field names and/or spaces.  If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 04:40 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 04:40 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #252

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 252



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 99 5:09:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uidømin.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - - --
- - - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - - -------------------------------------------------------------------

- - - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - - -	if I open the form on an exising record, it works great

- - - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - - ------_
- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uidømin.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UIDømin;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #252
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 05:06 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 05:06 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #253

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 253



Index:

Re: [INTERFACES] SQLDA
Undeliverable Message
Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 03 Mar 1999 04:04:06 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] SQLDA

> That's okay with me. Could we even use the PGresult structure as 
> SQLDA?

Possibly. All the access goes through a handle (presumably) and
subroutine calls or preprocessor constructs.

> I wonder where to find this standard.

The Date and Darwen book discusses some details, which is what I was
quoting. I have a draft of the standard itself. Want me to send it?

                   - Tom

------------------------------

Date: Wed, 3 Mar 99 5:34:35 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #251

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 251



Index:

postdrv ODBC driver problems

- ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter@alef.gcsu.edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved.  Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem.  Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query.  It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess.  Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now.  I can't get to the machines
I use Windows on until tomorrow.  It shouldn't be too difficult to
recreate the error if you want to look into it.  Just try to access a
table that uses mixed case field names and/or spaces.  If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

- ------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************

------------------------------

Date: Wed, 3 Mar 99 5:40:29 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #252

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 252



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 5:09:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid°min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - - - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - - - --
- - - - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - - - -------------------------------------------------------------------

- - - - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - - - -	if I open the form on an exising record, it works great

- - - - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - - - ------_
- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - - - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid°min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID°min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #252
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #253
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 05:35 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 05:35 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #254

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 254



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:06:19 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #253

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 253



Index:

Re: [INTERFACES] SQLDA
Undeliverable Message
Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 03 Mar 1999 04:04:06 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] SQLDA

> That's okay with me. Could we even use the PGresult structure as 
> SQLDA?

Possibly. All the access goes through a handle (presumably) and
subroutine calls or preprocessor constructs.

> I wonder where to find this standard.

The Date and Darwen book discusses some details, which is what I was
quoting. I have a draft of the standard itself. Want me to send it?

                   - Tom

- ------------------------------

Date: Wed, 3 Mar 99 5:34:35 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #251

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 251



Index:

postdrv ODBC driver problems

- - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter@alef.gcsu.edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved.  Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem.  Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query.  It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess.  Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now.  I can't get to the machines
I use Windows on until tomorrow.  It shouldn't be too difficult to
recreate the error if you want to look into it.  Just try to access a
table that uses mixed case field names and/or spaces.  If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

- - ------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************

- ------------------------------

Date: Wed, 3 Mar 99 5:40:29 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #252

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 252



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 5:09:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid×min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - - - - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - - - - --
- - - - - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - - - - -------------------------------------------------------------------

- - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - - - - -	if I open the form on an exising record, it works great

- - - - - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - - - - ------_
- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - - - - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid×min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID×min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #252
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #253
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #254
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 05:58 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 05:58 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #255

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 255



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:35:06 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #254

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 254



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:06:19 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #253

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 253



Index:

Re: [INTERFACES] SQLDA
Undeliverable Message
Undeliverable Message

- - ----------------------------------------------------------------------

Date: Wed, 03 Mar 1999 04:04:06 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] SQLDA

> That's okay with me. Could we even use the PGresult structure as 
> SQLDA?

Possibly. All the access goes through a handle (presumably) and
subroutine calls or preprocessor constructs.

> I wonder where to find this standard.

The Date and Darwen book discusses some details, which is what I was
quoting. I have a draft of the standard itself. Want me to send it?

                   - Tom

- - ------------------------------

Date: Wed, 3 Mar 99 5:34:35 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #251

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 251



Index:

postdrv ODBC driver problems

- - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter@alef.gcsu.edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved.  Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem.  Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query.  It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess.  Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now.  I can't get to the machines
I use Windows on until tomorrow.  It shouldn't be too difficult to
recreate the error if you want to look into it.  Just try to access a
table that uses mixed case field names and/or spaces.  If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

- - - ------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************

- - ------------------------------

Date: Wed, 3 Mar 99 5:40:29 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #252

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 252



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 5:09:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - - - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid+min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - - - - - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - - - - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - - - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - - - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - - - - - --
- - - - - - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - - - - - -------------------------------------------------------------------

- - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - - - - - -	if I open the form on an exising record, it works great

- - - - - - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - - - - - ------_
- - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - - - - - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid+min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID+min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #252
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #253
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #254
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #255
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 06:32 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 06:32 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #256

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 256



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:58:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #255

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 255



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:35:06 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #254

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 254



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:06:19 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #253

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 253



Index:

Re: [INTERFACES] SQLDA
Undeliverable Message
Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Wed, 03 Mar 1999 04:04:06 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] SQLDA

> That's okay with me. Could we even use the PGresult structure as 
> SQLDA?

Possibly. All the access goes through a handle (presumably) and
subroutine calls or preprocessor constructs.

> I wonder where to find this standard.

The Date and Darwen book discusses some details, which is what I was
quoting. I have a draft of the standard itself. Want me to send it?

                   - Tom

- - - ------------------------------

Date: Wed, 3 Mar 99 5:34:35 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #251

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 251



Index:

postdrv ODBC driver problems

- - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter@alef.gcsu.edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved.  Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem.  Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query.  It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess.  Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now.  I can't get to the machines
I use Windows on until tomorrow.  It shouldn't be too difficult to
recreate the error if you want to look into it.  Just try to access a
table that uses mixed case field names and/or spaces.  If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************

- - - ------------------------------

Date: Wed, 3 Mar 99 5:40:29 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #252

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 252



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 5:09:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - - - - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid+min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - - - - - - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - - - - - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - - - - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - - - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - - - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - - - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - - - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - - - - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - - - - - - --
- - - - - - - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - - - - - - -------------------------------------------------------------------

- - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - - - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - - - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - - - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - - - - - - -	if I open the form on an exising record, it works great

- - - - - - - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - - - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - - - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - - - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - - - - - - ------_
- - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid+min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID+min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #252
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #253
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #254
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #255
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #256
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 07:15 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 07:15 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #257

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 257



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 99 7:32:15 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #256

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 256



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:58:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #255

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 255



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:35:06 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #254

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 254



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:06:19 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #253

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 253



Index:

Re: [INTERFACES] SQLDA
Undeliverable Message
Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Wed, 03 Mar 1999 04:04:06 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] SQLDA

> That's okay with me. Could we even use the PGresult structure as 
> SQLDA?

Possibly. All the access goes through a handle (presumably) and
subroutine calls or preprocessor constructs.

> I wonder where to find this standard.

The Date and Darwen book discusses some details, which is what I was
quoting. I have a draft of the standard itself. Want me to send it?

                   - Tom

- - - - ------------------------------

Date: Wed, 3 Mar 99 5:34:35 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #251

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 251



Index:

postdrv ODBC driver problems

- - - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter@alef.gcsu.edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved.  Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem.  Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query.  It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess.  Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now.  I can't get to the machines
I use Windows on until tomorrow.  It shouldn't be too difficult to
recreate the error if you want to look into it.  Just try to access a
table that uses mixed case field names and/or spaces.  If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************

- - - - ------------------------------

Date: Wed, 3 Mar 99 5:40:29 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #252

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 252



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 5:09:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- - - - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - - - - - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid+min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - - - - - - - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - - - - - - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - - - - - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - - - - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - - - - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - - - - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - - - - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - - - - - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - - - - - - - --
- - - - - - - - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - - - - - - - -------------------------------------------------------------------

- - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - - - - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - - - - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - - - - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - - - - - - - -	if I open the form on an exising record, it works great

- - - - - - - - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - - - - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - - - - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - - - - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - - - - - - - ------_
- - - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid+min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID+min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #252
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #253
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #254
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #255
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #256
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #257
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-03 07:48 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-03 07:48 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #258

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 258



Index:

Re: pgsql-interfaces-digest V1 #256
Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 3 Mar 1999 17:29:36 +1100
From: "Nathan Dietsch" <ndietsch@mse.com.au>
Subject: Re: pgsql-interfaces-digest V1 #256

Hello,

Can someone please fix this, maybe remove the address from the list.

Regards,

Nathan Dietsch

- -----Original Message-----
From: pgsql-interfaces-digest <owner-pgsql-interfaces-digest@hub.org>
To: pgsql-interfaces-digest@hub.org <pgsql-interfaces-digest@hub.org>
Date: Wednesday, 3 March 1999 5:08
Subject: pgsql-interfaces-digest V1 #256


>
>pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number
256
>
>
>
>Index:
>
>Undeliverable Message
>
>----------------------------------------------------------------------
>
>Date: Wed, 3 Mar 99 6:58:40 +0100
>From: <MAILER-DAEMON@mail1.sfr.fr>
>Subject: Undeliverable Message
>
>To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
>Cc:
>Subject:       pgsql-interfaces-digest V1 #255
>
>Message not delivered to recipients below.  Press F1 for help with VNM
>error codes.
>
> VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST
>
>
>
>VNM3043 -- MAILBOX IS FULL
>
>   The message cannot be delivered because the
>   recipient's mailbox contains the maximum number of
>   messages, as set by the system administrator.  The
>   recipient must delete some messages before any
>   other messages can be delivered.
>    The maximum message limit for a user's mailbox is
>   10,000.  The default message limit is 1000 messages.
>   Administrators can set message limits using the
>   Mailbox  Settings function available in the
>   Manage User menu  (MUSER).
>
>   When a user's mailbox reaches the limit, the
>   user must delete some of the messages before
>   the mailbox can accept any more incoming messages.
>

------------------------------

Date: Wed, 3 Mar 99 8:15:33 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #257

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 257



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 7:32:15 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #256

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 256



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:58:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #255

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 255



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:35:06 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #254

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Wednesday, March 3 1999    Volume 01 : Number 254



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 6:06:19 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #253

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 253



Index:

Re: [INTERFACES] SQLDA
Undeliverable Message
Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Wed, 03 Mar 1999 04:04:06 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] SQLDA

> That's okay with me. Could we even use the PGresult structure as 
> SQLDA?

Possibly. All the access goes through a handle (presumably) and
subroutine calls or preprocessor constructs.

> I wonder where to find this standard.

The Date and Darwen book discusses some details, which is what I was
quoting. I have a draft of the standard itself. Want me to send it?

                   - Tom

- - - - - ------------------------------

Date: Wed, 3 Mar 99 5:34:35 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #251

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 251



Index:

postdrv ODBC driver problems

- - - - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 22:54:31 -0500
From: Ben Gunter <bgunter@alef.gcsu.edu>
Subject: postdrv ODBC driver problems

After version 0.95 of PgAccess was released (thanks so much for the
quick response!), I figured my problems with character case were
resolved.  Unfortunately, I tried to use the ODBC driver with MS Excel
97, and encountered the same problem.  Tables with mixed case field
names gave me errors, and tables with all lower case field names worked.

MS Query could see the table fine (named "Present") and reported the
names of the fields fine ("First Name" and "Last Name"), but it failed
when I actually executed the query.  It said: func_get_detail: no such
attribute or function "lastname".

This looks like the same problem I was having with PgAccess.  Am I
missing something?

I'm using version 6.40.0004 of the ODBC driver, and PostgreSQL 6.4.2.

I'm sorry I don't have the logs right now.  I can't get to the machines
I use Windows on until tomorrow.  It shouldn't be too difficult to
recreate the error if you want to look into it.  Just try to access a
table that uses mixed case field names and/or spaces.  If you still want
to see the logs, let me know; I'll try to send them tomorrow.

Thanks,
Ben

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #251
**************************************

- - - - - ------------------------------

Date: Wed, 3 Mar 99 5:40:29 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #252

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 252



Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 5:09:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #250

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 250



Index:

Undeliverable Message

- - - - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 4:19:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #249

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 249



Index:

Undeliverable Message

- - - - - - - - ----------------------------------------------------------------------

Date: Wed, 3 Mar 99 3:12:40 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #248

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 248



Index:

Re: [INTERFACES] Foreign Keys
Undeliverable Message
RE: [INTERFACES] Foreign Keys

- - - - - - - - - ----------------------------------------------------------------------

Date: Tue, 02 Mar 1999 17:10:30 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> Here is the psqlodbc.log file.  The first time the form opens, it correctly
> opens the first rentalorder.  I immediately moved to the new record in
> Access which opens a message box with an ODBC error (no description).  I the
> blank rental order looks okay but the rental order lines records all have
> errors.  Even if I move back to a valid record, the order lines will show
> only errors.
>

Here's what I see.  The first problems are the permission denied errors.   It may be due to the
uid+min.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn3944104, query"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

conn3944104, query,"membership"."lastname" ,"memberservices"."serviceid"  FROM "memberservices","membership"
WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND ("membership"."memberid" "memberservices"."memberid" ) ) ORDER BY "membership"."lastname" ,"membership"."firstname"  '
ERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'

conn3944104,
SQLDriverConnect(out)
conn3944104, query,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance" ,"seminarbalance" ,"selected"
,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender" ,"email" ,"optname"
,"recordtype"  FROM "membership" '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func


The second problem is this:

conn3237224, query"RentalOrders" WHERE ("rentalorderid" ERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func

Since postgres will not recognize the syntax (where 'col' "isnull".  I was hoping someone would have added the ability for the parser to handle this at
some point (Hey Dave, maybe you could contribute something here man :-).


Byron

- - - - - - - - - ------------------------------

Date: Wed, 3 Mar 99 0:10:24 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #247

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 247



Index:

Undeliverable Message

- - - - - - - - - - ----------------------------------------------------------------------

Date: Tue, 2 Mar 99 23:25:36 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #246

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Tuesday, March 2 1999     Volume 01 : Number 246



Index:

How can I get more result fields in pgaccess visual query builder?
Re: passing variable between cgi
Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?
RE: [INTERFACES] passing variable between cgi
Re: [INTERFACES] mod_auth_pg95
Read-Only ODBC, MS/ACCESS
Persistent connection in PostGresSQL
Re: [INTERFACES] Read-Only ODBC, MS/ACCESS
RE: [INTERFACES] Foreign Keys
JDBC Will not compile Error 139?
JDBC Will not compile Error 139?
Re: [INTERFACES] Foreign Keys
RE: [INTERFACES] Foreign Keys

- - - - - - - - - - - ----------------------------------------------------------------------

Date: Mon, 1 Mar 1999 23:40:13 -0500 (EST)
From: "Stan Brown" <stanb@awod.com>
Subject: How can I get more result fields in pgaccess visual query builder?

	I am doing some prtotyping on a new  project, and I have a couple of
	questions.

	How can I get more result fieds in the pgaccess visual query builder?

	Can someone give me a brief explantaion of, or point me to some
	documentaion for using the forms builder in pgaccess?

	Thanks.

- - - - - - - - - - - - -- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
- - - - - - - - - - - - -- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
- - - - - - - - - - - - -
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.

- - - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 08:27:37 +0200 (EET)
From: Razvan Marcus <marcus@twf2.twf.ro>
Subject: Re: passing variable between cgi

  You can use <input typefrom a cgi to another.

	Argus 

On Mon, 1 Mar 1999, hoelc wrote:

> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program) through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
> 
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi program will run and get
> some data from Postgres, then when the user click another button, the other cgi
> will be triggerred to process certain data got by the previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi according to the
> user choice ...
> 
> I am using the embedded SQL (ecpg) method to write the cgi ( C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.rutgers.edu
> 

- - - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:37:30 +0200
From: Constantin Teodorescu <teo@flex.ro>
Subject: Re: [INTERFACES] How can I get more result fields in pgaccess visual  query builder?

Stan Brown wrote:
> 
> How can I get more result fieds in the pgaccess visual query builder?

Just click on the result field area zone and drag it to the left or
right.
That will scroll the region and allows you to see more result fields

> Can someone give me a brief explantaion of, or point me to some
> documentaion for using the forms builder in pgaccess?

Unfortunately no.
There is a formdemo.sql dumped database in the .tar.gz that shows some
of the forms features.
I had not time to document forms module. I want to enhance it and maybe
I will write a small HOWTO.

All the best,
- - - - - - - - - - - - -- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

- - - - - - - - - - - ------------------------------

Date: Mon, 1 Mar 1999 17:15:55 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] passing variable between cgi

When the first CGI program is run and generates the second HTML page with
the second form on it, have it include some form fields of type 'hidden'.
The values of these fields would be the data you wish pass to the second
cgi.

You can then retrieve the data in the same way as you do for your other
fields when the form is submitted.

Shameless plug: Check out libcgi at http://www.vale-it.demon.co.uk/freeware
for a relatively easy way to get the form data.

HTH

Dave.

- - - - - - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of hoelc
> Sent: 01 March 1999 15:06
> To: linux-net@vger.rutgers.edu; PostgreSQL Interfaces
> Subject: [INTERFACES] passing variable between cgi
>
>
> Hello,
> I am setting up PostgreSQL (postgresql-6.4.2) database in
> Linux (Linux 2.0.27)
> system, and want to access the database with cgi ( C program)
> through Apache
> (version 1.1) server.  My application involve a few cgi programmes.
> I can not figure out how to pass varibles between cgi programmes.
>
> My application involve some thing like this:
>     In a HTML page, when the user click a button, a cgi
> program will run and get
> some data from Postgres, then when the user click another
> button, the other cgi
> will be triggerred to process certain data got by the
> previous cgi, so, I will
> need to pass the data get by the first cgi to the second cgi
> according to the
> user choice ...
>
> I am using the embedded SQL (ecpg) method to write the cgi

> C program ) to get
> data from postgresql-6.4.2.
> How should I pass variable between these C program?  What are
> the common methods
> to develop this kind of application?
> Please advice.
> Thank you.
> LCH
>
>
>

- - - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 09:33:34 +0100
From: Giuseppe Tanzilli <g.tanzilli@eurolink.it>
Subject: Re: [INTERFACES] mod_auth_pg95

Hi,
sorry for the trouble
I was unable to update the record in the modules.apache.org.
Anyway it's at:
ftp://ftp.eurolink.it/pub/linux/postgreSQL/

bye

yves@asua.vlaanderen.net wrote:

> Hello,
>
> Does anyone have a port of the module mod_auth_pg95 for Apache 1.3.x ? I
> tried compiling it, had to change some function calls but it doesn't work
> :-(
>
> -Yves

- - - - - - - - - - - - --
- - - - - - - - - - - - -----------------------------------------------------------------
 Giuseppe Tanzilli               Flashnet S.p.A. Telecomunicazioni
 mailto: g.tanzilli@flashnet.it  Sede di Frosinone
 Eurolink S.r.l.                 mailto: info.frosinone@flashnet.it
 Tel: +39-0775-830012            http://www.flashnet.it
 Fax: +39-0775-201321            EUnet Business Partner
 http://www.eurolink.it          AIIP and ANFOV associated
 PGP Key: finger giuseppe@king.fr.flashnet.it
- - - - - - - - - - - - -------------------------------------------------------------------

- - - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 11:59:25 +0200
From: Nicolas Boretos <nicolasb@maich.gr>
Subject: Read-Only ODBC, MS/ACCESS

Hello,

I am experimenting with the postdrv and seems to work in Excel, but as
read only in Acess97. Any ideas?
Thank you,
Nicolas Boretos

- - - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 12:11:10 +0200
From: CIMPOESU Teodor <teo@digiro.net>
Subject: Persistent connection in PostGresSQL

I have some questions for you all,
What is the difference between a persistent connection and a regular one
in postgres?
If I read /server-status after some queries with pg_pconnect() I see a
lot of active sessions there.
In which cases it is reasonable to use a persistent conection and in
which is not?
10x.

- - - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 07:04:44 -0600
From: "Mark A. Schwenk" <mas@wellthot.com>
Subject: Re: [INTERFACES] Read-Only ODBC, MS/ACCESS

It seems that the ODBC driver creates a read-only connection by default (at
least with Access). You need to turn this off as follows.

Try to create a new ODBC link from Access to PostgreSQL. When you see the
PostgreSQL Driver Setup dialog, click the Driver button in the the Options
(Advanced). This will open an Advanced Options (Driver) dialog. In this
dialog box, uncheck the ReadOnly (Default) checkbox.

I hope this solves your problem.

- - - - - - - - - - - - -Mark Schwenk
 WellThot Inc.
 http://wellthot.com

- - - - - - - - - - - - -----Original Message-----
From: Nicolas Boretos <nicolasb@maich.gr>
To: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Tuesday, March 02, 1999 3:50 AM
Subject: [INTERFACES] Read-Only ODBC, MS/ACCESS


>Hello,
>
>I am experimenting with the postdrv and seems to work in Excel, but as
>read only in Acess97. Any ideas?
>Thank you,
>Nicolas Boretos
>

- - - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 12:09:26 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I have narrowed the problem down a little.  Here is what I have discovered
so far:

- - - - - - - - - - - - -	sql.log (odbc trace facility) has no references to primary or
foreign keys

- - - - - - - - - - - - -	if I open the form on an exising record, it works great

- - - - - - - - - - - - -	if I open the form on a new record, an error occurs in a select
statement that basically locks up the subform

- - - - - - - - - - - - -	the error occurs on "select orderlineid from orderlines where
orderid Access gets the orderid of the current record, it is null.  Access gets all
orderlineids associated with the orderid.  This fails on the new record.
When the form is on a valid record, Access then gets the orderline record
for each orderlineid returned by the previous statement.  This seems to be a
long way around getting data, but I don't have any control over this
interaction.

It appears that I cant add new records using Access97 with PostgreSQL as my
database engine.  Has anyone used Access97 or other similar front end tools
to interface with a PostgreSQL database?  Any suggestions on what I might
try next to work around this problem?

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Thursday, February 25, 1999 2:12 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have created the following trigger on the parent/master table
(orders):
	>
	> CREATE TRIGGER Orderlines_fkey
	>     BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
	>     EXECUTE PROCEDURE check_foreign_key ();
	>
	> check_foreign_key() actually deletes rows from the orderlines
table when
	> every a row is deleted from orders.  This triggers works great.
Access,
	> however, is still not recognizing the foreign key relationship
between
	> orders and orderlines.  Any other suggestions?
	>
	> Thanks, Michael
	>

	Yeah, there is more we can try.  First of all, we need to verify
that Access
	is actually calling SQLForeignKeys.   Can you get a "trace" log of
the
	session?  This would be the "sql.log" file which contains all api
calls to
	odbc.  Make sure the file is clear beforehand.  Then run the test.
Quit
	Access, turn tracing off and there's your logfile.  You can send it
to me.

	It might also be helpful to have the commlog file (produced by the
	driver)...usually "psqlodbc.log".   It may have a process id number
appended
	to the filename so make sure you get the right one.

	Byron

	

- - - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 11:26:11 -0700 (MST)
From: tperry@grumpy.it.as.ex.state.ut.us
Subject: JDBC Will not compile Error 139?

I have tried to run javac on CallableStatement and it seems to work ok
manually, but when I use the make it gives me this error?  Any ideas?  I
am new to the JDK, I am using 1.1.7 installed in the /usr/local/java
directory.  Any Help would be appreciated.

Tim 



bash$ make
javac postgresql/CallableStatement.java
CLASSPATH is not set!
make: *** [postgresql/CallableStatement.class] Error 1

bash$ export CLASSPATHbash$ make
javac postgresql/CallableStatement.java
No library path set.
make: *** [postgresql/CallableStatement.class] Error 139

- - - - - - - - - - - ------------------------------

Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Foreign Keys

Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid > Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron

- - - - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 14:51:44 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

- - - - - - - - - - - - ------_Content-Type: text/plain

Here is the psqlodbc.log file.  The first time the form opens, it correctly
opens the first rentalorder.  I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description).  I the
blank rental order looks okay but the rental order lines records all have
errors.  Even if I move back to a valid record, the order lines will show
only errors.

 <<psqlodbc_270.log>> 

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 12:52 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> I have narrowed the problem down a little.  Here is what I have
discovered
	> so far:
	>
	> -       sql.log (odbc trace facility) has no references to primary
or
	> foreign keys
	>
	> -       if I open the form on an exising record, it works great
	>
	> -       if I open the form on a new record, an error occurs in a
select
	> statement that basically locks up the subform
	>
	> -       the error occurs on "select orderlineid from orderlines
where
	> orderid record.
	> Access gets the orderid of the current record, it is null.  Access
gets all
	> orderlineids associated with the orderid.  This fails on the new
record.
	> When the form is on a valid record, Access then gets the orderline
record
	> for each orderlineid returned by the previous statement.  This
seems to be a
	> long way around getting data, but I don't have any control over
this
	> interaction.
	>
	> It appears that I cant add new records using Access97 with
PostgreSQL as my
	> database engine.  Has anyone used Access97 or other similar front
end tools
	> to interface with a PostgreSQL database?  Any suggestions on what
I might
	> try next to work around this problem?
	>
	>

	Logs, logs, logs (see my last response).  I don't know how else to
put it!

	Its next to impossible to figure things out without the logs.

	Byron

	

- - - - - - - - - - - - ------_Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filenameContent-Location: ATT-0-6389C710D9D0D211A1B4080009DCB9A8-P
	S6BBE%7E1.LOG

conn3237224, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, queryconn3237224, query    [ fetched 0 rows ]
conn3237224, SQLDriverConnect(out)conn3237224, queryERROR from backend during send_query: 'ERROR:  msysconf: Table does not exist.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inB, buffer_filled_outuffer_read_inB
conn3237224, query    [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, queryconn3632808, query    [ fetched 0 rows ]
conn3632808, SQLDriverConnect(out)conn3632808, query    [ fetched 1 rows ]
conn3723168, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, queryconn3723168, query    [ fetched 0 rows ]
conn3723168, SQLDriverConnect(out)conn3723168, query    [ fetched 10 rows ]
conn3723168, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3802280, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, queryconn3802280, query    [ fetched 0 rows ]
conn3802280, SQLDriverConnect(out)conn3812792, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, queryconn3812792, query    [ fetched 0 rows ]
conn3812792, SQLDriverConnect(out)conn3812792, query    [ fetched 570 rows ]
conn3802280, query    [ fetched 163 rows ]
conn3812792, SQLDisconnect
conn3802280, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket56, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_in@, buffer_filled_outuffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket84, reverserrornumberrrormsg            buffer_in3791272, buffer_out3898984
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3791272, buffer_out3890856
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  memberservices: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socket48, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inE, buffer_filled_outuffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, queryERROR from backend during send_query: 'ERROR:  membership: Permission denied.'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3944104, stmt3950776, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3944104, status6
            sock3797296, stmts3646224, lobj_type            ---------------- Socket Info - -------------------------------
            socketB8, reverserrornumberrrormsg            buffer_in3890856, buffer_out3791272
            buffer_filled_inA, buffer_filled_outuffer_read_inA
conn3944104, SQLDisconnect
conn3237224, queryERROR from backend during send_query: 'ERROR:  parser: parse error at or near "null"'
STATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc3237224, stmt3550944, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters3645616, parameters_allocated
                 statement_type
tement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            - ------------------------------------------------------------
            henv3237168, conn3237224, status6
            sock3243592, stmts3251960, lobj_type            ---------------- Socket Info - -------------------------------
            socket24, reverserrornumberrrormsg            buffer_in3243672, buffer_out3247816
            buffer_filled_inH, buffer_filled_outuffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllGlobal Options: Version                disable_optimizer, unique_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, queryconn3944104, query    [ fetched 0 rows ]
conn3944104, SQLDriverConnect(out)conn3944104, query    [ fetched 570 rows ]
conn3237224, query    [ fetched 163 rows ]
conn3944104, SQLDisconnect
conn3632808, query    [ fetched 10 rows ]
conn3632808, SQLDisconnect
conn3237224, SQLDisconnect

- - - - - - - - - - - - ------_
- - - - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #246
**************************************

- - - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #247
**************************************

- - - - - - - - - ------------------------------

Date: Tue, 2 Mar 1999 18:56:33 -0600 
From: Michael Davis <michael.davis@prevuenet.com>
Subject: RE: [INTERFACES] Foreign Keys

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.  

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?  

	-----Original Message-----
	From:	Byron Nikolaidis [SMTP:byronn@insightdist.com]
	Sent:	Tuesday, March 02, 1999 3:11 PM
	To:	Michael Davis
	Cc:	'pgsql-interfaces@postgreSQL.org'; David Hartwig
	Subject:	Re: [INTERFACES] Foreign Keys



	Michael Davis wrote:

	> Here is the psqlodbc.log file.  The first time the form opens, it
correctly
	> opens the first rentalorder.  I immediately moved to the new
record in
	> Access which opens a message box with an ODBC error (no
description).  I the
	> blank rental order looks okay but the rental order lines records
all have
	> errors.  Even if I move back to a valid record, the order lines
will show
	> only errors.
	>

	Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
	uid+min.  You could probably set the uid to something more
reasonable in your connect string
	in Access.


	conn3944104, query	ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

	conn3944104, queryFROM "membership" ORDER BY
	"lastname" ,"firstname"  '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

	conn3944104, query,"membership"."firstname"
	,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
	WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" 	"memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
	ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

	conn3944104,
	
SQLDriverConnect(out)432;UID+min;PWDWVERSIONINGMTABLESONNSETTINGS
	conn3944104, query,"middleinitial" ,"lastname" ,"surname"
	,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
	,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
	,"recordtype"  FROM "membership" '
	ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
	STATEMENT ERROR: funcwhile executing the query'



	The second problem is this:

	conn3237224, queryFROM "rentalorderlines"
	"RentalOrders" WHERE ("rentalorderid" 	ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
	STATEMENT ERROR: funcwhile executing the query'


	Since postgres will not recognize the syntax (where 'col' it only recognizes
	"isnull".  I was hoping someone would have added the ability for the
parser to handle this at
	some point (Hey Dave, maybe you could contribute something here man
:-).


	Byron

- - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #248
**************************************

- - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #249
**************************************

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #250
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #252
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #253
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #254
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #255
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #256
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #257
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #258
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 02:43 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 02:43 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn=26282108, SQLDriverConnect( in)='DSN=pgsql test;', fDriverCompletion=1
DSN info: DSN='pgsql test',server='foo',port='5432',dbase='test',user='tester',passwd='testing'
          readonly='0',protocol='',showoid='0',fakeoidindex='0',showsystable='0'
          conn_settings=''
          translation_dll='',translation_option=''
conn=26282108, SQLDriverConnect(out)='DSN=pgsql test;DATABASE=test;SERVER=tux;PORT=5432;UID=tester;PWD=testing;READONLY=0;PROTOCOL=;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS='
Global Options: Version='06.30.0250', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
                disable_optimizer=1, unique_index=0, use_declarefetch=0
                text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1
                extra_systable_prefixes='dd_;', conn_settings=''
conn=26282108, query=' '
conn=26282108, query='set DateStyle to 'ISO''
conn=26282108, query='set geqo to 'OFF''
conn=26282108, query='select oid from pg_type where typname='lo''
    [ fetched 0 rows ]
CONN ERROR: func=SQLSetConnectOption, desc='fOption=1041, vParam=351504640', errnum=5, errmsg='Driver does not support setting this connect option'
            ------------------------------------------------------------
            henv=27328644, conn=26282108, status=1, num_stmts=16
            sock=27328660, stmts=27328700, lobj_type=-999
            ---------------- Socket Info -------------------------------
            socket=23, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=26288400, buffer_out=26292500
            buffer_filled_in=28, buffer_filled_out=0, buffer_read_in=28
CONN ERROR: func=SQLSetConnectOption, desc='fOption=1042, vParam=351504652', errnum=5, errmsg='Driver does not support setting this connect option'
            ------------------------------------------------------------
            henv=27328644, conn=26282108, status=1, num_stmts=16
            sock=27328660, stmts=27328700, lobj_type=-999
            ---------------- Socket Info -------------------------------
            socket=23, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=26288400, buffer_out=26292500
            buffer_filled_in=28, buffer_filled_out=0, buffer_read_in=28
conn=26282108, query='select relname, usename, relhasrules from pg_class, pg_user where relkind = 'r' and relname like 'pbcattbl' and relname !~ '^pg_|^dd_' and relname !~ '^xinv[0-9]+' and int4out(usesysid) = int4out(relowner)order by relname'
    [ fetched 0 rows ]
conn=26282108, query='select relname, usename, relhasrules from pg_class, pg_user where relkind = 'r' and relname like 'PBCATTBL' and relname !~ '^pg_|^dd_' and relname !~ '^xinv[0-9]+' and int4out(usesysid) = int4out(relowner)order by relname'
    [ fetched 0 rows ]
conn=26282108, query='BEGIN'
conn=26282108, query='CREATE TABLE pbcattbl (pbt_tnam char(33) NOT NULL)'
conn=26282108, query='COMMIT'
conn=26282108, query='BEGIN'
conn=26282108, query='CREATE UNIQUE INDEX pbcatt_x ON pbcattbl (pbt_tnam ,pbt_ownr )'
ERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn=26282108, query='COMMIT'
STATEMENT ERROR: func=SC_execute, desc='', errnum=17, errmsg='Error creating the table'
                 - ------------------------------------------------------------
                 hdbc=26282108, stmt=26296600, result=0
                 manual_result=0, prepare=0, internal=0
                 bindings=0, bindings_allocated=0
                 parameters=0, parameters_allocated=0
                 statement_type=4, statement='CREATE UNIQUE INDEX pbcatt_x ON pbcattbl (pbt_tnam ,pbt_ownr )'
                 stmt_with_params='CREATE UNIQUE INDEX pbcatt_x ON pbcattbl (pbt_tnam ,pbt_ownr )'
                 data_at_exec=-1, current_exec_param=-1, put_data=0
                 currTuple=-1, current_col=-1, lobj_fd=-1
                 maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, scroll_concurrency=1
                 cursor_name='SQL_CUR01914118'
                 ----------------QResult Info - -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=10, errmsg='ERROR:  DefineIndex: attribute "pbt_ownr" not found'
            ------------------------------------------------------------
            henv=27328644, conn=26282108, status=1, num_stmts=16
            sock=27328660, stmts=27328700, lobj_type=-999
            ---------------- Socket Info -------------------------------
            socket=23, reverse=0, errornumber=0, errormsg='(null)'
            buffer_in=26288400, buffer_out=26292500
            buffer_filled_in=2, buffer_filled_out=0, buffer_read_in=2
conn=26282108, query='select relname, usename, relhasrules from pg_class, pg_user where relkind = 'r' and relname !~ '^pg_|^dd_' and relname !~ '^xinv[0-9]+' and int4out(usesysid) = int4out(relowner)order by relname'
    [ fetched 1 rows ]
conn=26282108, SQLDisconnect

- ------
------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- ------END GEEK CODE BLOCK------

------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- ------END GEEK CODE BLOCK------

------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- --------------C2CA35DE7AE8AC2B6B8140A9--

------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- -Mark


- -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- -----------------------------------------------------------------

------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el døa Wed, 24 Mar 1999 15:57:04 
- -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 03:34 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 03:34 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - ------
- ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - ------END GEEK CODE BLOCK------

- ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - ------END GEEK CODE BLOCK------

- ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - --------------C2CA35DE7AE8AC2B6B8140A9--

- ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - -Mark


- - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - -----------------------------------------------------------------

- ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d°a Wed, 24 Mar 1999 15:57:04 
- - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 04:18 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 04:18 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - ------
- - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - ------END GEEK CODE BLOCK------

- - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - ------END GEEK CODE BLOCK------

- - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - -Mark


- - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - -----------------------------------------------------------------

- - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d×a Wed, 24 Mar 1999 15:57:04 
- - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 04:44 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 04:44 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #285

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 285



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - ------
- - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - ------END GEEK CODE BLOCK------

- - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - ------END GEEK CODE BLOCK------

- - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - -Mark


- - - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - - -----------------------------------------------------------------

- - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d+a Wed, 24 Mar 1999 15:57:04 
- - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 05:06 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 05:06 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #286

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 286



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:44:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #285

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 285



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - - ------
- - - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - ------END GEEK CODE BLOCK------

- - - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - ------END GEEK CODE BLOCK------

- - - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - - -Mark


- - - - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - - - -----------------------------------------------------------------

- - - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d+a Wed, 24 Mar 1999 15:57:04 
- - - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #286
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 05:30 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 05:30 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #287

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 287



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:06:46 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #286

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 286



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:44:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #285

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 285



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - - - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - - - ------
- - - - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - ------END GEEK CODE BLOCK------

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - ------END GEEK CODE BLOCK------

- - - - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - - - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - - - -Mark


- - - - - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - - - - -----------------------------------------------------------------

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d+a Wed, 24 Mar 1999 15:57:04 
- - - - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - - - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #286
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #287
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 05:48 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 05:48 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #288

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 288



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:30:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #287

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 287



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:06:46 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #286

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 286



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:44:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #285

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 285



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - - - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - - - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - - - - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - - - - ------
- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - ------END GEEK CODE BLOCK------

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - ------END GEEK CODE BLOCK------

- - - - - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - - - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - - - - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - - - - -Mark


- - - - - - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - - - - - -----------------------------------------------------------------

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - - - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d+a Wed, 24 Mar 1999 15:57:04 
- - - - - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - - - - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - - - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #286
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #287
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #288
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 06:16 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 06:16 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #289

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 289



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:48:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #288

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 288



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:30:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #287

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 287



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:06:46 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #286

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 286



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:44:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #285

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 285



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - - - - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - - - - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - - - - - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - - - - - ------
- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - - - - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - - - - - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - - - - - -Mark


- - - - - - - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - - - - - - -----------------------------------------------------------------

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - - - - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d+a Wed, 24 Mar 1999 15:57:04 
- - - - - - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - - - - - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - - - - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #286
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #287
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #288
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #289
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 06:39 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 06:39 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #290

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 290



Index:

Undeliverable Message

----------------------------------------------------------------------

Date: Thu, 25 Mar 99 7:16:08 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #289

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 289



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:48:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #288

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 288



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:30:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #287

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 287



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:06:46 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #286

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 286



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:44:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #285

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 285



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- - - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - - - - - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - - - - - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - - - - - - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - - - - - - ------
- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - - - - - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - - - - - - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - - - - - - -Mark


- - - - - - - - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - - - - - - - -----------------------------------------------------------------

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - - - - - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d+a Wed, 24 Mar 1999 15:57:04 
- - - - - - - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - - - - - - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - - - - - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #286
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #287
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #288
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #289
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #290
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-03-25 07:15 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-03-25 07:15 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #291

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 291



Index:

I can not import text file...  Errno Undeliverable Message

----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 22:01:28 -0800
From: Michael Irschick <mirschick@penguinsystems.com>
Subject: I can not import text file...  Errno 
I have not been able to insert a text file into my postgres table.

Here is the file.
- -rw-rw-r--   1 mirschic mirschic       14 Mar 24 21:26 test.txt
/home/mirschick/test.txt
"test","test"

- ----

oprs
ERROR:  COPY command, running in backend with effective uid 100, could
not open file '/home/mirschick/test.txt' for reading.  Errno Permission denied (13).
oprs
- ---

So what is going on?  I tried diff text files, and diff tables I always
get the same error.  (Errno 
my username is mirschick
I created the text file as mirschick
I created the table, and database as mirschick.

- ---

Thanks for any help..  I am a newbie....

mirschick@penguinsystems.com

------------------------------

Date: Thu, 25 Mar 99 7:39:31 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #290

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 290



Index:

Undeliverable Message

- ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 7:16:08 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #289

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 289



Index:

Undeliverable Message

- - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:48:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #288

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest    Thursday, March 25 1999    Volume 01 : Number 288



Index:

Undeliverable Message

- - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:30:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #287

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 287



Index:

Undeliverable Message

- - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 6:06:46 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #286

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 286



Index:

Undeliverable Message

- - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:44:39 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #285

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 285



Index:

Undeliverable Message

- - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 5:18:27 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #284

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 284



Index:

Undeliverable Message

- - - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 4:34:50 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #283

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 283



Index:

Undeliverable Message

- - - - - - - - ----------------------------------------------------------------------

Date: Thu, 25 Mar 99 3:43:09 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #282

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - - - - - - - - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest   Wednesday, March 24 1999   Volume 01 : Number 282



Index:

Re: [INTERFACES] why there's only char type?
RE: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] Converting microsoft access to postgresql
Re: [INTERFACES] JDBC Query performance
[ANN] pg.el -- Emacs Lisp interface for PostgreSQL
Re: [INTERFACES] Invalid BLOB Length
Re: [INTERFACES] why there's only char type?
Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.
Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 
[Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]
Resignation
MkLinux & ODBC compile error
pgaccess - can I tab through columns without the mouse? 
Re: [INTERFACES] Resignation
radius+PAM+PostgreSQL
Re: [INTERFACES] Resignation
PgAdmin

- - - - - - - - - ----------------------------------------------------------------------

Date: Wed, 24 Mar 1999 16:03:14 -0800
From: "Daniel" <daniel@ids.org.my>
Subject: Re: [INTERFACES] why there's only char type?

This is a multi-part message in MIME format.

- - - - - - - - - - ------Content-Type: text/plain;
	charsetContent-Transfer-Encoding: 7bit

After many times of reconfiguring the ODBC connection profile, recreating
the database, and even re-installing the postODBC, I think the problem lies
on the fact that Powerbuilder needs a set of its own system (or 'catalog')
tables in order to work properly in the *visual* mode. Because right now
Powerbuilder reports an error ("Catalog table could not be created and are
not available for use") everytime I start a connection to the database.
Interestingly, I could create a table with INT4 and CHAR fields from
Powerbuilder's text mode and it worked, but in visual mode, it could only
see the 1st field and ignored the 2nd.

Anyway, thanks for suggesting looking into the odbc trace log. The log files
attached with this mail created right after the following process:
1) Re-create the database test.
2) In Powerbuilder, delete & then re-configure the ODBC connection profile,
uncheck 'ReadOnly'.
3) Start the trace log (from ODBC Data Source Admin).
4) Connect to the database, and got the error msg "Catalog...." as mentioned
above.
5) Still can connect to the database. At this point if I am to create a new
table, Powerbuilder will show me only the 'char' type. But as far as the log
files are conecerned, I didnt do anything.
6) Disconnect from the database (by connecting to another db, i.e. Sybase).

If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
that a problem of PostODBC or Powerbuilder? Thanks for any help.

Daniel




- - - - - - - - - - -----Original Message-----
From: Byron Nikolaidis <byronn@insightdist.com>
To: Daniel <daniel@ids.org.my>
Cc: pgsql-interfaces@hub.org <pgsql-interfaces@hub.org>
Date: Monday, March 22, 1999 11:31 AM
Subject: Re: [INTERFACES] why there's only char type?


>
>
>Daniel wrote:
>
>> Last week I got PostgreSQL 6.3.x running with -i switch and then created
a
>> test database. On Win95 end, postODBC was installed and my PowerBuilder
>> could connect to the database. Then I tried to transfer the data from
Sybase
>> SQL Anywhere to Postgres via Powerbuilder's pipeline mechanism. In
>> Powerbuilder I did notice that there were some unfamiliar database type
in
>> Postgres such as INT4 to represent Sybase's INTEGER type and got me
really
>> excited. However I couldnt create anything in Postgres because I forgot
to
>> uncheck the "read-only" option when i setup the odbc connection, but
that's
>> different story.
>>
>> After coming back from weekend, I tried to do the transfer of data again,
>> and I did make sure the "read-only" option has been unchecked. But right
now
>> I encounter a new problem: I found that I could no longer see other data
>> type in Postgres except CHAR. I've tried all the possible setting in odbc
>> connection but it still doesn't help. What seems to be the problem?
Please
>> help.
>>
>
>I'm not sure why you would only see 'char'.  If the application is using
the
>odbc function SQLGetTypeInfo() to retrieve the data types, then maybe it is
>looking for data types that support a certain feature.  Maybe this is
>configurable.  I'm not really sure what your application is doing.
>
>If you want, you could send an odbc trace log of the session so we could at
>least see if it is calling SQLGetTypeInfo() and retrieving the results.
>Otherwise, there is nothing else I can do.
>
>Byron
>
>

- - - - - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename
PC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBvZiBtYWlsIC0tPg0KDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRUeXBlSW5mbyANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgMCA8U1FMX0FMTF9UWVBFUz4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVYSVQgIFNRTEdldFR5cGVJbmZvICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNTKQ0K
CQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJU1dPUkQgICAgICAgICAgICAgICAg
ICAgICAgICAwIDxTUUxfQUxMX1RZUEVTPg0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRU5URVIgU1FMR2V0RnVuY3Rpb25zIA0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0
OWZmYTANCgkJVVdPUkQgICAgICAgICAgICAgICAgICAgICAgIDU5IA0KCQlVV09SRCAqICAgICAg
ICAgICAgIDB4MDA2M2UzMTYNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVY
SVQgIFNRTEdldEZ1bmN0aW9ucyAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJ
SERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCVVXT1JEICAgICAgICAgICAgICAgICAg
ICAgICA1OSANCgkJVVdPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzE2ICgxKQ0KDQpQQjA1MCAg
ICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMU2V0U3RtdE9wdGlvbiANCgkJSFNU
TVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAg
ICAgOSA8U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoN
ClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxTZXRTdG10T3B0aW9u
ICB3aXRoIHJldHVybiBjb2RlIDEgKFNRTF9TVUNDRVNTX1dJVEhfSU5GTykNCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSA8
U1FMX1JPV1NFVF9TSVpFPg0KCQlVRFdPUkQgICAgICAgICAgICAgICAgICAgIDE2DQoNCgkJRElB
RyBbMDFTMDJdIFJlcXVlc3RlZCB2YWx1ZSBjaGFuZ2VkLjsKRHJpdmVyIGRvZXMgbm90IHN1cHBv
cnQgc2V0dGluZyB0aGlzIGNvbm5lY3Qgb3B0aW9uICgxNikgDQoNClBCMDUwICAgICAgICAgICBm
ZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAgICAgICAgICAgICAg
MHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAg
ICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZTJlMCAo
TllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZTMzMA0KCQlXQ0hBUiAqICAgICAg
ICAgICAgIDB4MDA2M2RlZTAgDQoJCVNXT1JEICAgICAgICAgICAgICAgICAgICAgIDUxMiANCgkJ
U1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlMzI2DQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2
MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUgMCAoU1FMX1NVQ0NF
U1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAg
ICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFS
ICogICAgICAgICAgICAgMHgwMDYzZTJlMCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAg
MHgwMDYzZTMzMCAoMTYpDQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZGVlMCBbICAgICAg
NzddICJSZXF1ZXN0ZWQgdmFsdWUgY2hhbmdlZC47XCBhRHJpdmVyIGRvZXMgIg0KCQlTV09SRCAg
ICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTMy
NiAoNzcpDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxHZXRT
dG10T3B0aW9uIA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAg
ICAgICAgICAgICAgICAgICAgICA5IA0KCQlQVFIgICAgICAgICAgICAgICAgMHgwMDRkZDY5Yw0K
DQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMR2V0U3RtdE9wdGlv
biAgd2l0aCByZXR1cm4gY29kZSAwIChTUUxfU1VDQ0VTUykNCgkJSFNUTVQgICAgICAgICAgICAg
ICAweDAxM2EwZDQ0DQoJCVVXT1JEICAgICAgICAgICAgICAgICAgICAgICAgOSANCgkJUFRSICAg
ICAgICAgICAgICAgIDB4MDA0ZGQ2OWMNCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA0ZTg5NzQgWyAgICAgNDAzXSAiQ1JFQVRFIFRBQkxF
IHBiY2F0Y29sIChwYmNfdG5hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfdGlkID8/Pz8/ICxwYmNf
b3duciBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY25hbSBjaGFyKDMzKSBOT1QgTlVMTCxwYmNfY2lk
ID8/Pz8/ICxwYmNfbGFibCBjaGFyKDI1NCkgLHBiY19scG9zID8/Pz8/ICxwYmNfaGRyIGNoYXIo
MjU0KSAscGJjX2hwb3MgPz8/Pz8gLHBiY19qdGZ5ID8/Pz8/ICxwYmNfbWFzayBjaGFyKDMxKSAs
cGJjX2Nhc2UgPz8/Pz8gLHBiY19oZ2h0ID8/Pz8/ICxwYmNfd2R0aCA/Pz8/PyAscGJjX3B0cm4g
Y2hhcigzMSkgLHBiY19ibWFwIGNoYXIoMSkgLHBiY19pbml0IGNoYXIoMjU0KSAscGJjX2NtbnQg
Y2hhcigyNTQpICxwYmNfZWRpdCBjaGFyKDMxKSAscGJjX3RhZyBjaGFyKDI1NCkgKSINCgkJU0RX
T1JEICAgICAgICAgICAgICAgICAgIDQwMw0KDQpQQjA1MCAgICAgICAgICAgZmZmYjcwNjM6ZmZm
YzJiNzMJRVhJVCAgU1FMRXhlY0RpcmVjdCAgd2l0aCByZXR1cm4gY29kZSAtMSAoU1FMX0VSUk9S
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVUNIQVIgKiAgICAgICAgICAg
ICAweDAwNGU4OTc0IFsgICAgIDQwM10gIkNSRUFURSBUQUJMRSBwYmNhdGNvbCAocGJjX3RuYW0g
Y2hhcigzMykgTk9UIE5VTEwscGJjX3RpZCA/Pz8/PyAscGJjX293bnIgY2hhcigzMykgTk9UIE5V
TEwscGJjX2NuYW0gY2hhcigzMykgTk9UIE5VTEwscGJjX2NpZCA/Pz8/PyAscGJjX2xhYmwgY2hh
cigyNTQpICxwYmNfbHBvcyA/Pz8/PyAscGJjX2hkciBjaGFyKDI1NCkgLHBiY19ocG9zID8/Pz8/
ICxwYmNfanRmeSA/Pz8/PyAscGJjX21hc2sgY2hhcigzMSkgLHBiY19jYXNlID8/Pz8/ICxwYmNf
aGdodCA/Pz8/PyAscGJjX3dkdGggPz8/Pz8gLHBiY19wdHJuIGNoYXIoMzEpICxwYmNfYm1hcCBj
aGFyKDEpICxwYmNfaW5pdCBjaGFyKDI1NCkgLHBiY19jbW50IGNoYXIoMjU0KSAscGJjX2VkaXQg
Y2hhcigzMSkgLHBiY190YWcgY2hhcigyNTQpICkiDQoJCVNEV09SRCAgICAgICAgICAgICAgICAg
ICA0MDMNCg0KCQlESUFHIFtTMDAwMV0gRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlOwpFUlJPUjog
IHBhcnNlcjogcGFyc2UgZXJyb3IgYXQgb3IgbmVhciAiIiAoMTcpIA0KDQpQQjA1MCAgICAgICAg
ICAgZmZmYjcwNjM6ZmZmYzJiNzMJRU5URVIgU1FMRXJyb3JXIA0KCQlIRU5WICAgICAgICAgICAg
ICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAgICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1U
ICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3
YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAgICAgIDB4MDA2M2U4MGMNCgkJV0NIQVIgKiAg
ICAgICAgICAgICAweDAwNjNlM2JjIA0KCQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIg
DQoJCVNXT1JEICogICAgICAgICAgICAgMHgwMDYzZTgwMg0KDQpQQjA1MCAgICAgICAgICAgZmZm
YjcwNjM6ZmZmYzJiNzMJRVhJVCAgU1FMRXJyb3JXICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9T
VUNDRVNTKQ0KCQlIRU5WICAgICAgICAgICAgICAgIDB4MDE0OWZjZmMNCgkJSERCQyAgICAgICAg
ICAgICAgICAweDAxNDlmZmEwDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2U3YmMgKE5ZSSkgDQogCQlTRFdPUkQgKiAgICAgICAg
ICAgIDB4MDA2M2U4MGMgKDE3KQ0KCQlXQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2UzYmMgWyAg
ICAgIDY3XSAiRXJyb3IgY3JlYXRpbmcgdGhlIHRhYmxlO1wgYUVSUk9SOiAiDQoJCVNXT1JEICAg
ICAgICAgICAgICAgICAgICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNlODAy
ICg2NykNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjczCUVOVEVSIFNRTEZyZWVT
dG10IA0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAg
ICAgICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZm
ZmMyYjczCUVYSVQgIFNRTEZyZWVTdG10ICB3aXRoIHJldHVybiBjb2RlIDAgKFNRTF9TVUNDRVNT
KQ0KCQlIU1RNVCAgICAgICAgICAgICAgIDB4MDEzYTBkNDQNCgkJVVdPUkQgICAgICAgICAgICAg
ICAgICAgICAgICAxIDxTUUxfRFJPUD4NCg0KDQo8LS0gc25pcHBlZCwgdG8gdHJpbSBkb3duIHRo
ZSBzaXplIG9mIG1haWwgLS0+DQoNCg0KUEIwNTAgICAgICAgICAgIGZmZmI3MDYzOmZmZmMyYjcz
CUVOVEVSIFNRTEV4ZWNEaXJlY3QgDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0K
CQlVQ0hBUiAqICAgICAgICAgICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9u
YW1lLCBwYmVfZWRpdCwgcGJlX3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBi
ZV9mbGFnIGZyb20gcGJjYXRlZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlT
RFdPUkQgICAgICAgICAgICAgICAgICAgIC0zDQoNClBCMDUwICAgICAgICAgICBmZmZiNzA2Mzpm
ZmZjMmI3MwlFWElUICBTUUxFeGVjRGlyZWN0ICB3aXRoIHJldHVybiBjb2RlIC0xIChTUUxfRVJS
T1IpDQoJCUhTVE1UICAgICAgICAgICAgICAgMHgwMTNhMGQ0NA0KCQlVQ0hBUiAqICAgICAgICAg
ICAgIDB4MDA2M2YyNjAgWyAgICAgIC0zXSAic2VsZWN0IHBiZV9uYW1lLCBwYmVfZWRpdCwgcGJl
X3R5cGUsIHBiZV9jbnRyLCBwYmVfd29yaywgcGJlX3NlcW4sIHBiZV9mbGFnIGZyb20gcGJjYXRl
ZHQgb3JkZXIgYnkgcGJlX25hbWUsIHBiZV9zZXFuXCAwIg0KCQlTRFdPUkQgICAgICAgICAgICAg
ICAgICAgIC0zDQoNCgkJRElBRyBbMDhTMDFdIEVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVl
cnk7CkVSUk9SOiAgcGJjYXRlZHQ6IFRhYmxlIGRvZXMgbm90IGV4aXN0LiAoMSkgDQoNClBCMDUw
ICAgICAgICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFTlRFUiBTUUxFcnJvclcgDQoJCUhFTlYgICAg
ICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJDICAgICAgICAgICAgICAgIDB4MDE0OWZmYTAN
CgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2EwZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAg
MHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAqICAgICAgICAgICAgMHgwMDYzZjE5OA0KCQlX
Q0hBUiAqICAgICAgICAgICAgIDB4MDA2M2VkNDggDQoJCVNXT1JEICAgICAgICAgICAgICAgICAg
ICAgIDUxMiANCgkJU1dPUkQgKiAgICAgICAgICAgICAweDAwNjNmMThlDQoNClBCMDUwICAgICAg
ICAgICBmZmZiNzA2MzpmZmZjMmI3MwlFWElUICBTUUxFcnJvclcgIHdpdGggcmV0dXJuIGNvZGUg
MCAoU1FMX1NVQ0NFU1MpDQoJCUhFTlYgICAgICAgICAgICAgICAgMHgwMTQ5ZmNmYw0KCQlIREJD
ICAgICAgICAgICAgICAgIDB4MDE0OWZmYTANCgkJSFNUTVQgICAgICAgICAgICAgICAweDAxM2Ew
ZDQ0DQoJCVdDSEFSICogICAgICAgICAgICAgMHgwMDYzZjE0OCAoTllJKSANCiAJCVNEV09SRCAq
ICAgICAgICAgICAgMHgwMDYzZjE5OCAoMSkNCgkJV0NIQVIgKiAgICAgICAgICAgICAweDAwNjNl
ZDQ4IFsgICAgICA3Ml0gIkVycm9yIHdoaWxlIGV4ZWN1dGluZyB0aGUgcXVlcnk7XCBhRVJSIg0K
CQlTV09SRCAgICAgICAgICAgICAgICAgICAgICA1MTIgDQoJCVNXT1JEICogICAgICAgICAgICAg
MHgwMDYzZjE4ZSAoNzIpDQoNCg0KPC0tIHNuaXBwZWQsIHRvIHRyaW0gZG93biB0aGUgc2l6ZSBv
ZiBtYWlsIC0tPg0KDQoNCg
- - - - - - - - - - ------Content-Type: application/octet-stream;
	nameContent-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename
conn&282108, SQLDriverConnect( in)DSN info: DSN          readonly          conn_settings          translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query    [ fetched 0 rows ]
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in(, buffer_filled_outuffer_read_in(
conn&282108, query    [ fetched 0 rows ]
conn&282108, query    [ fetched 0 rows ]
conn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, queryERROR from backend during send_query: 'ERROR:  DefineIndex: attribute "pbt_ownr" not found'
conn&282108, querySTATEMENT ERROR: func                 - ------------------------------------------------------------
                 hdbc&282108, stmt&296600, result
                 manual_resultparernal
                 bindingsindings_allocated
                 parameters
rameters_allocated
                 statement_typeJtement                 stmt_with_params                 data_at_exec                 currTuple                 maxRowst_sizeyset_sizeursor_typeroll_concurrency
                 cursor_name                 ----------------QResult Info - -------------------------------
CONN ERROR: func            ------------------------------------------------------------
            henv'328644, conn&282108, status6
            sock'328660, stmts'328700, lobj_type            ---------------- Socket Info -------------------------------
            socket#, reverserrornumberrrormsg            buffer_in&288400, buffer_out&292500
            buffer_filled_in+uffer_filled_outuffer_read_in
conn&282108, query    [ fetched 1 rows ]
conn&282108, SQLDisconnect

- - - - - - - - - - ------
- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 08:08:45 -0000
From: Dave Page <dpage@vale-housing.co.uk>
Subject: RE: [INTERFACES] Converting microsoft access to postgresql

(Shameless plug!) Try pgAdmin. It is available at:

http://www.pgadmin.freeserve.co.uk

pgAdmin has a migration wizard that will copy an mdb or another ODBC
datasource table by table. It will create the table (datatypes are mapable),
copy the data if required and then create the required indexes.

Regards,

Dave.

- - - - - - - - - - --
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!


> -----Original Message-----
> From: owner-pgsql-interfaces@postgreSQL.org
> [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Frederic De
> Leersnijder
> Sent: 24 March 1999 01:03
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] Converting microsoft access to postgresql
>
>
> I'm looking for a program to convert a microsoft access mdb
> to postgres.
>
> Thnx.
>
> Frederic De Leersnijder
>
>

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:07:19 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

pgAdmin will do the job.  It does it through the ODBC interface.  For big
databases, though, I've had better luck dumping tables to text files and
doing a bulk copy back into PostgreSQL.

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - - - - -----------------------------------------------------------------------
	The Arkansas legislature passed a law that states that the Arkansas
River can rise no higher than to the Main Street bridge in Little Rock.

- - - - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 03:08:34 -0500 (EST)
From: "Brett W. McCoy" <bmccoy@lan2wan.com>
Subject: Re: [INTERFACES] Converting microsoft access to postgresql

On Wed, 24 Mar 1999, Frederic De Leersnijder wrote:

> I'm looking for a program to convert a microsoft access mdb to postgres.

Oops.  Forgot the URL for pgAdmin: http://www.pgadmin.freeserve.co.uk

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
- - - - - - - - - - -----------------------------------------------------------------------
Do not handicap your children by making their lives easy.
		-- Robert Heinlein

- - - - - - - - - - -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
- - - - - - - - - - ------END GEEK CODE BLOCK------

- - - - - - - - - ------------------------------

Date: Mon, 22 Mar 1999 22:51:26 -0800
From: "Postgres mailing lists" <postgres@weblynk.com>
Subject: Re: [INTERFACES] JDBC Query performance

That's what's interesting about this to me. Using psql, piping the results
to a file, it is less than a second, and the CPU time goes to 50% idle. The
file that I piped to ends up about 3.5MB's. Jdbc is about 90 seconds, and 0%
idle. I've put trace statements in, so I'm pretty sure that to return from
the executeQuery(sql); method is about 90 seconds. If you can't reproduce
it, then maybe I could send you the table that I query, or maybe you could
send me a table that you query of similiar size (~1200 rows, 25 columns, no
indexes, most columns are varchar() or float8() ), that it performs well on.
Rich.


>Hmmm, this is interesting. Does the cpu time match when the same queries
>are run through PSQL?
>
>Peter
>
>--
>Peter T Mount, IT Section
>petermount@it.maidstone.gov.uk
>Anything I write here are my own views, and cannot be taken as the
>official words of Maidstone Borough Council
>
>-----Original Message-----
>From: Postgres mailing lists [mailto:postgres@weblynk.com]
>Sent: Sunday, March 21, 1999 7:11 PM
>To: pgsql-interfaces@postgreSQL.org
>Subject: Re: [INTERFACES] JDBC Query performance
>
>
>>At 11:07 +0200 on 18/03/1999, Peter Mount wrote:
>>
>>
>>>
>>> The delay is because the driver currently retrieves the entire result
>>> into a Vector() before returning the ResultSet.
>>
>>Couldn't it also be because of Java's usage of network sockets compared
>to
>>psql's use of unix sockets?
>>
>You know, I also noticed that it is the postgres back-end process which
>is
>using all the CPU time during the query. Doesn't sound like Vector
>operations to me, which should cause the java process to eat all the CPU
>time.
>Rich.
>
>

- - - - - - - - - ------------------------------

Date: 24 Mar 1999 10:48:42 +0100
From: Eric Marsden <emarsden@mail.dotcom.fr>
Subject: [ANN] pg.el -- Emacs Lisp interface for PostgreSQL

pg.el is a socket-level interface to PostgreSQL for GNU Emacs (text
editor extraordinaire). The module is capable of type coercions from a
range of SQL types to the equivalent Emacs Lisp type. It currently
supports neither crypt or Kerberos authentication, nor large objects,
nor the v6.4 protocol.

The code (version 0.1) is available under GPL from

   <URL:http://www.chez.com/emarsden/downloads/pg.el;


Please note that this is a programmer's API, and doesn't provide any
form of user interface. Example:
   
 (defun demo ()
    (interactive)
    (let* ((conn (pg:connect "template1" "postgres" "postgres"))
           (res (pg:exec conn "SELECT * from scshdemo WHERE a       (message "status is %s"   (pg:result res 'status))
      (message "metadata is %s" (pg:result res 'attributes))
      (message "data is %s"     (pg:result res 'tuples))
      (pg:disconnect conn)))

- - - - - - - - - - -- 
Eric Marsden
emarsden @ mail.dotcom.fr
It's elephants all the way down

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:35:41 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] Invalid BLOB Length

PostgreSQL Server wrote:

> I am using Borland C++ Builder 3.0 with PostgreSQL 6.4.2 and the
> latest ODBC driver from ftp.postgresql.org.
>
> I created a table users that looks like this:
>
> CREATE TYPE lo (
>         internallength >         externallenght >         input >         output >         send >         receive >         default >         passedbyvalue);
>
> CREATE TABLE users (
>         userid int4,
>         username varchar(255),
>         userimage lo);
>
> When I try and insert an image, the app returns "Invalid BLOB Length".
>
> What am I doing Wrong?
>
> Thanks
>
>                 Travis


Are there any errors in the driver's commlog ("psqlodbc.log") file?  You
can also check the odbc trace log.  If you can't figure anything out, you
can try sending me the logs and I could take a look.

Byron

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:24:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Re: [INTERFACES] why there's only char type?

Daniel wrote:

> If you examine the Sql.log, it did call SQLGetTypeInfo(). But the error
> occured when exiting SQLSetStmtOption. Could that be the whole problem? Is
> that a problem of PostODBC or Powerbuilder? Thanks for any help.
>
> Daniel
>

The below excerpt from the log I think reveals the problem.  You are using an older version
of the driver (according to the psqlodbc.log -- Versionsetting the rowset size to anything greater than 1.  You need to get the latest driver!
Go to http://www.insightdist.com/psqlodbc.PB050           fffb7063:fffc2b73 ENTER
SQLGetTypeInfo  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>

PB050           fffb7063:fffc2b73 EXIT  SQLGetTypeInfo  with return code 0 (SQL_SUCCESS)
  HSTMT               0x013a0d44
  SWORD                        0 <SQL_ALL_TYPES>


PB050           fffb7063:fffc2b73 ENTER SQLSetStmtOption
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

PB050           fffb7063:fffc2b73 EXIT  SQLSetStmtOption  with return code 1
(SQL_SUCCESS_WITH_INFO)
  HSTMT               0x013a0d44
  UWORD                        9 <SQL_ROWSET_SIZE>
  UDWORD                    16

  DIAG [01S02] Requested value changed.;
Driver does not support setting this connect option (16)


, fetch0, socket@96, unknown_sizes
x_varchar_size%4, max_longvarchar_size@94
                disable_optimizer_index_declarefetch
                text_as_longvarchars_longvarcharools_as_char
                extra_systable_prefixes
- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:25:06 +0100
From: Ordini <sferac@bo.nettuno.it>
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count  function.

bug: HAVING IN SUBQUERIES
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a known bug.
Jose'

> > We are trying to execute a query that has several sub-queries embedded
> > in it.  Below is a snippet of the sql code.
> >
> > "Select ordnum from ordinace where dept> > (Select ordnum from squareview where square> > ordnum from keywordview where keyword> > Gathering' group by ordnum having count(ordnum) 
> >
> > The two tables in the sub-queries (squareview and keywordview) or
> > views created between two tables.
> > There are roughly about 20000 records in the keywordview view.
> >
> > When we execute the query, failing at the keywordview subquery, saying
> > the aggregate function in the having clause must appear on the right
> > side. (?)  When we take the having clause out, and strictly have the
> > group by, it takes 30secs to 3mins. to return with the valid
> > recordset.
> >
> > The funny thing is, as a stand alone query on it's own, the
> > keywordview query works fine.  It's very quick and has no problem with
> > the having clause.
> >
> > I was wondering if anyone else has either had this problme using
> > aggregate functions with the having clause in a subquery, or could
> > anyone give me any information of successfully executing something
> > similar to this.
> >
> > Any infomation would be appreciated.
> >
> > Thanks in advance,
> >
> > Steve
> > steve@ctlno.com

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 09:54:49 -0500
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Problem using Having in a sub-query wit the Count function. 

Matthew <matt@ctlno.com> writes:
>> "Select ordnum from ordinace where dept>> (Select ordnum from squareview where square>> ordnum from keywordview where keyword>> Gathering' group by ordnum having count(ordnum) 

I wonder whether the parser could be getting confused by the multiple
distinct uses of the same name "ordnum" in this query?  In other words,
maybe you'd have better luck if the inner queries read something like

select
k.ordnum from keywordview k where k.keywordGathering' group by k.ordnum having count(k.ordnum) 

Without that, it might be thinking that count(ordnum) refers to the
ordnum in the outer select.

If that is it, it's probably a bug, but I'm not sure what the standard
says about how to interpret ambiguous names in this context...

			regards, tom lane

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 10:20:44 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: [Fwd: [INTERFACES] type error inserting large obj, Win32 ODBC]

This is a multi-part message in MIME format.
- - - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit




- - - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <36F8F7B8.4A396607@insightdist.com>
Date: Wed, 24 Mar 1999 09:33:28 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Sam@OConnor.net
Subject: Re: [INTERFACES] type error inserting large obj, Win32 ODBC
References: <36F5C26E.49702D13@netspace.net.au> <36F679B8.CF2B577C@insightdist.com> <36F8E290.73F534CF@netspace.net.au>
Content-Type: text/plain; charsetContent-Transfer-Encoding: 7bit



Sam O'Connor wrote:

> I have attached the logs.
> Thankyou very much for your help.
>
> Sam O'Connor
>
>

I don't really see the problem.  It seems more like there is something wrong on the postgres side.

create type lo (internallengthNxternallength,input                default
If this is what you typed in to create the "lo" type, then it should work.  Try inserting a row manually into the table, say something like:

insert into image ( 1, 2, 'stuff', 5);

If this fails, then maybe there is something weird with the i/o routines (int4in, int4out), in which case, you should seek more help from perhaps the "general"
mailing list.

Byron



- - - - - - - - - - --------------C2CA35DE7AE8AC2B6B8140A9--

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:57:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Subject: Resignation

Hi everyone,

I just wanted to let everyone know that today is my last day at Insight
Distribution Systems.  There will be no one else at Insight taking over
the development and support of the ODBC driver since it was more of a
side project and no one knows anything about it anyway.  Also, in case
anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
I was solely representing the Postgres faction at Insight.

I would like to continue my role as primary development and support of
the odbc driver to the extent possible.  But since there are a lot of
factors involved, I'm just not sure what that extent might be.  IF I can
keep my account at Insight, I should be able to test out things and
maybe add new functionality/features, if I have the time.

As far as the Insight-Psqlodbc web site goes,  I have talked with some
people and the plan is to keep it alive.  I have asked that I be allowed
to update it as necessary and they seemed agreeable to that.

I also will remain subscribed to the "interfaces" mailing list for as
long as possible (I have unsubscribed to all others).  I should be able
to check the mailing list perhaps once or twice a week.  I will have to
see how it goes with my new job before I know for sure.  But the thing
is, since I do not currently have any internet access at home, I have to
rely on Insight to allow me to keep dialing in and doing that.

I would like to say that I have enjoyed working with everyone and I
really enjoyed contributing to the PostgreSQL project.  I have learned
alot during that time and hope that I have contributed positively.  I
wish everyone the best and I sincerely hope that Postgres continues to
grow at the incredible rate it has been.

Regards,

Byron

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 16:50:55 -0500
From: Mark <mlundquist@bvsdps.com>
Subject: MkLinux & ODBC compile error

I have successfully compiled & run PostgreSQL on MkLinux many times.  I
added the  --with-odbc arguement and now I get an error when I compile.

misc.c:100: request for member `overflow_arg_area' in something not a structure
or union
misc.c:111: warning: passing arg 3 of `vfprintf' from incompatible pointer type
misc.c:94: warning: `args' might be used uninitialized in this function
misc.c:100: warning: `__ptr' might be used uninitialized in this function
gmake[2]: *** [misc.o] Error 1
gmake[2]: Leaving directory
`/usr/src/pgsql/postgresql-6.4.2/src/interfaces/odbc
'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/src/pgsql/postgresql-6.4.2/src/interfaces'
gmake: *** [all] Error 2


Has anyone seen this and can help me (or anyone even reading this)?


MkLinux DR3  (RedHat Linux 5.1)
PostgreSQL 6.4.2

- - - - - - - - - - -Mark


- - - - - - - - - - -----------------------------------------------------------------
   Mark Lundquist               Bell Atlantic Video Services
   mlundquist@bvsdps.com        1880 Campus Commons Drive
                                Reston, VA  20191
- - - - - - - - - - -----------------------------------------------------------------

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 23:03:19 +0100
From: Wybo Dekker <wybo@servalys.hobby.nl>
Subject: pgaccess - can I tab through columns without the mouse? 

Hi,

Normally one can jump from column to column using the tab key, but in
pgaccess this does not seem to work. Is there another way?

- - - - - - - - - - -- 
Hartelijke groet, Wybo Dekker
___________________Servalys Analytical Chemistry Services__________________
wybo@servalys.hobby.nl | Deilsedijk 60                 | tel +31-345-652164
www.hobby.nl/~servalys | 4158 CH Deil, The Netherlands | fax +31-345-652383

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:56:15 -0300
From: Sergio <ser@perio.unlp.edu.ar>
Subject: Re: [INTERFACES] Resignation

Byron Nikolaidis <byronn@insightdist.com> el d+a Wed, 24 Mar 1999 15:57:04 
- - - - - - - - - - -0500, escribi<:

>Hi everyone,
>
>I just wanted to let everyone know that today is my last day at Insight
>Distribution Systems.  There will be no one else at Insight taking over
>the development and support of the ODBC driver since it was more of a
>side project and no one knows anything about it anyway.  Also, in case
>anyone didn't know, Dave Hartwig left the company about 3 weeks ago, so
>I was solely representing the Postgres faction at Insight.
>
>I would like to continue my role as primary development and support of
>the odbc driver to the extent possible.  But since there are a lot of
>factors involved, I'm just not sure what that extent might be.  IF I can
>keep my account at Insight, I should be able to test out things and
>maybe add new functionality/features, if I have the time.
>
>As far as the Insight-Psqlodbc web site goes,  I have talked with some
>people and the plan is to keep it alive.  I have asked that I be allowed
>to update it as necessary and they seemed agreeable to that.
>
>I also will remain subscribed to the "interfaces" mailing list for as
>long as possible (I have unsubscribed to all others).  I should be able
>to check the mailing list perhaps once or twice a week.  I will have to
>see how it goes with my new job before I know for sure.  But the thing
>is, since I do not currently have any internet access at home, I have to
>rely on Insight to allow me to keep dialing in and doing that.
>
>I would like to say that I have enjoyed working with everyone and I
>really enjoyed contributing to the PostgreSQL project.  I have learned
>alot during that time and hope that I have contributed positively.  I
>wish everyone the best and I sincerely hope that Postgres continues to
>grow at the incredible rate it has been.

Oh, my... this make my sad day...
The only thing I can do is to offer a web site (in the form of
http://perio.unlp.edu.ar/psqlodbc) that you don't have
to maintain (I will do that with whatever changes you request), but
my permanent connection to Internet is a little slow (28.8).

But, /please/, keep us informed about your movements.

Sergio

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 14:03:59 -0800
From: Matthew Hixson <hixson@frozenwave.com>
Subject: radius+PAM+PostgreSQL

Hello,
  I was wondering if anyone out there was using the Cistron radius server with
PAM support who is doing the authentication against a PostgreSQL database. 
That is the setup I would like to use.  However, I'm unsure of how everything
fits together.
  Could someone provide me with an overview of their system, or if someone with
more of a clue than I have could explain to me how I would piece these things
together (via config files and necessary modules) I would be forever grateful.
  Thanks in advance,
    -M@
- - - - - - - - - - --
Matthew Hixson - CIO  
FroZenWave Communications   
http://www.frozenwave.com

- - - - - - - - - ------------------------------

Date: Wed, 24 Mar 1999 15:16:05 -0800
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] Resignation

Byron,

I, along with many others I'm sure, have come to depend greatly on your
work with the odbc driver. Your work has made PostgreSQL a viable solution
where win clients are required. Thank you and good luck with your new work!
Also, if I (or anyone else) can be of any assistance in keeping you active
here, please pipe up ;-)

Cheers!

Ken

- - - - - - - - - ------------------------------

Date: Thu, 25 Mar 1999 02:55:51 +0100
From: "Frederic De Leersnijder" <frederic.de.leersnijder@pandora.be>
Subject: PgAdmin

Hi,
I'm having trouble starting PgAdmin.

I'll describe what I have done so far.

1) pgAdmin requires the PostODBC driver which is available here. You must
set check the 'Show Column' and 'Fake Index' options under 'OID Options' for
pgAdmin to work

I have installed the PostODBC driver. I haven't set show column and fake
index because I can't find the OID options.

 2) As of v6.3.208, pgAdmin also requires Microsoft's MDAC 2.0 package (the
Redistribution Typical Setup version). This decreases the size of the
pgAdmin download significantly, and helps to eliminate ODBC version conflict
errors.

Done this.

3) Installing Pgadmin.

4) Opening the ODBC 32 panel in the control panel (I'm using 98)
Tab --> user dns -> MS Access driver -> configure --> database select --> In
my case h:\mediatheek.mdb

5) Starting Pgadmin

6) The logon dialog box is in front of me
datasource --> Microsoft Access 97 database.
Username:                     (none)
Pass: 			       (nonea

7) The program freezes. This happens in 98 and in NT 4.0


Does someone recognize this problem?

Thnx. for the advice that will soon be on it's way (hopefully   :o))    )

- - - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #282
**************************************

- - - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #283
**************************************

- - - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #284
**************************************

- - - - - - ------------------------------

End of pgsql-interfaces-digest V1 #285
**************************************

- - - - - ------------------------------

End of pgsql-interfaces-digest V1 #286
**************************************

- - - - ------------------------------

End of pgsql-interfaces-digest V1 #287
**************************************

- - - ------------------------------

End of pgsql-interfaces-digest V1 #288
**************************************

- - ------------------------------

End of pgsql-interfaces-digest V1 #289
**************************************

- ------------------------------

End of pgsql-interfaces-digest V1 #290
**************************************

------------------------------

End of pgsql-interfaces-digest V1 #291
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-05-23 04:27 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-05-23 04:27 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #355

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Saturday, May 22 1999     Volume 01 : Number 355



Index:

ECPG feature
jdbc - getArray
jdbc - number of updated rows
Error with JDBC
Re: [INTERFACES] ECPG feature

----------------------------------------------------------------------

Date: Fri, 21 May 1999 21:53:08 +0200
From: "Pavel PaJaSoft Janousek" <janousek@fonet.cz>
Subject: ECPG feature

    Hi,

    ECPG is very powerfull, I have one idea..

    If I have contruction ala:

    if (cond)
        exec sql ....
    else
        exec sql...

    Yes, this MUST be for right run as there:

    if (cond)
    {
        exec sql...
    }
    else
    {
        exec sql ...
    }

    So, why this brackets ('{' and '}') doesn't include ECPG? It may include
this brackets before and after every 'EXEC SQL' command...

    I know, that this is some modifications in output of parser... may
anybody do this modifications?

- -------------------------------------------------------------------------
Pavel Janousek (PaJaSoft)                         FoNet, spol. s r. o.
Vyvoj software, sprava siti, Unix, Web, Y2K     Anenska 11, 602 00  Brno
E-mail: mailto:Janousek@FoNet.Cz                Tel.: +420  5  4324 4749
SMS:    mailto:P.Janousek@SMS.Paegas.Cz         Fax.: +420  5  4324 4751
WWW:    http://WWW.FoNet.Cz/                  E-mail: mailto:Info@FoNet.Cz
- --------------------------------------------------------------------------

------------------------------

Date: Sat, 22 May 1999 12:24:28 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - getArray

Is there any working implementation of getArray? When it is
expected to be implemented in JDBC interface?


PS. I'm new this list, so if answers to my questions are in any kind
of faqs or were answered recently, please give a link to it.

PS2. I was trying to search archive-list, but it seems to be not
working...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

------------------------------

Date: Sat, 22 May 1999 12:35:10 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - number of updated rows

Please tell me how to get to know how many rows has method
executeUpdate affected. According to documentation
<cut>
Returns:
        either the row count for INSERT, UPDATE or DELETE ...
</cut>
this method should return number of updated rows, but it always
returns 1. It's a feature(bug) of postgresql jdbc-driver?

The only solution for my problem, that I made up is:

turn off auto-commit

select count(*) from table
where tID
- -- now i (probably)know number of updated rows

update table set ...
where tID

commit

turn on auto-commit
- -- stupid, isn't it ...

PS. remember that I'm new here...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

------------------------------

Date: Sat, 22 May 1999 04:36:47 -0700 (PDT)
From: Peter Garner <peter_garner@yahoo.com>
Subject: Error with JDBC

Hi All

I am using Postgres 6.5b and the JDBC that came with
it.   Under RH6.0 I get the following error attempting
to connect :

java.sql.SQLException: Something unusual has occured
to cause the driver to fail. Please report this
exception: java.sql.SQLException: Unknown Response
Type: K
	at postgresql.Driver.connect(Driver.java:106)
	at
java.sql.DriverManager.getConnection(DriverManager.java:83)
	at
java.sql.DriverManager.getConnection(DriverManager.java:126)
	at
crazy.pete.jnews.nntp.NewsReader.connectDBMS(NewsReader.java:95)
	at NewsMain.main(NewsMain.java:64)

I suspect this is something to do with a network
service not being properly started.  (I doubt it has
anything to do with the postmaster, since I am using
the identical startup script that worked with RH5.2.)
Oh, BTW both postmaster and the JDBC CLIENT are
running
on the same machine.  What service could I have
forgotten to start that is preventing TCP sockets from
working?   Thanks!
Peace,
Peter

We are Microsoft of Borg, you will be assimilated!!!
Resistance is fut...  ***BZZZRT***  THUD!!!
[General Protection Fault in MSBorg32.DLL]
Please contact the vendor of this Borg for more information
_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com

------------------------------

Date: Sat, 22 May 1999 22:15:28 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     if (cond)
>         exec sql ....
>     else
>         exec sql...
> 
>     Yes, this MUST be for right run as there:
> 
>     if (cond)
>     {
>         exec sql...
>     }
>     else
>     {
>         exec sql ...
>     }

This looks like a bug. I will check it asap.

Michael
- -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

End of pgsql-interfaces-digest V1 #355
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-05-24 04:28 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-05-24 04:28 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #356

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest      Sunday, May 23 1999      Volume 01 : Number 356



Index:

Undeliverable Message
Re: [INTERFACES] What to use to get number of tuples in a query
Re: [INTERFACES] ECPG feature

----------------------------------------------------------------------

Date: Sun, 23 May 99 5:27:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #355

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Saturday, May 22 1999     Volume 01 : Number 355



Index:

ECPG feature
jdbc - getArray
jdbc - number of updated rows
Error with JDBC
Re: [INTERFACES] ECPG feature

- ----------------------------------------------------------------------

Date: Fri, 21 May 1999 21:53:08 +0200
From: "Pavel PaJaSoft Janousek" <janousek@fonet.cz>
Subject: ECPG feature

    Hi,

    ECPG is very powerfull, I have one idea..

    If I have contruction ala:

    if (cond)
        exec sql ....
    else
        exec sql...

    Yes, this MUST be for right run as there:

    if (cond)
    {
        exec sql...
    }
    else
    {
        exec sql ...
    }

    So, why this brackets ('{' and '}') doesn't include ECPG? It may include
this brackets before and after every 'EXEC SQL' command...

    I know, that this is some modifications in output of parser... may
anybody do this modifications?

- - -------------------------------------------------------------------------
Pavel Janousek (PaJaSoft)                         FoNet, spol. s r. o.
Vyvoj software, sprava siti, Unix, Web, Y2K     Anenska 11, 602 00  Brno
E-mail: mailto:Janousek@FoNet.Cz                Tel.: +420  5  4324 4749
SMS:    mailto:P.Janousek@SMS.Paegas.Cz         Fax.: +420  5  4324 4751
WWW:    http://WWW.FoNet.Cz/                  E-mail: mailto:Info@FoNet.Cz
- - --------------------------------------------------------------------------

- ------------------------------

Date: Sat, 22 May 1999 12:24:28 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - getArray

Is there any working implementation of getArray? When it is
expected to be implemented in JDBC interface?


PS. I'm new this list, so if answers to my questions are in any kind
of faqs or were answered recently, please give a link to it.

PS2. I was trying to search archive-list, but it seems to be not
working...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- ------------------------------

Date: Sat, 22 May 1999 12:35:10 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - number of updated rows

Please tell me how to get to know how many rows has method
executeUpdate affected. According to documentation
<cut>
Returns:
        either the row count for INSERT, UPDATE or DELETE ...
</cut>
this method should return number of updated rows, but it always
returns 1. It's a feature(bug) of postgresql jdbc-driver?

The only solution for my problem, that I made up is:

turn off auto-commit

select count(*) from table
where tID
- - -- now i (probably)know number of updated rows

update table set ...
where tID

commit

turn on auto-commit
- - -- stupid, isn't it ...

PS. remember that I'm new here...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- ------------------------------

Date: Sat, 22 May 1999 04:36:47 -0700 (PDT)
From: Peter Garner <peter_garner@yahoo.com>
Subject: Error with JDBC

Hi All

I am using Postgres 6.5b and the JDBC that came with
it.   Under RH6.0 I get the following error attempting
to connect :

java.sql.SQLException: Something unusual has occured
to cause the driver to fail. Please report this
exception: java.sql.SQLException: Unknown Response
Type: K
	at postgresql.Driver.connect(Driver.java:106)
	at
java.sql.DriverManager.getConnection(DriverManager.java:83)
	at
java.sql.DriverManager.getConnection(DriverManager.java:126)
	at
crazy.pete.jnews.nntp.NewsReader.connectDBMS(NewsReader.java:95)
	at NewsMain.main(NewsMain.java:64)

I suspect this is something to do with a network
service not being properly started.  (I doubt it has
anything to do with the postmaster, since I am using
the identical startup script that worked with RH5.2.)
Oh, BTW both postmaster and the JDBC CLIENT are
running
on the same machine.  What service could I have
forgotten to start that is preventing TCP sockets from
working?   Thanks!
Peace,
Peter

We are Microsoft of Borg, you will be assimilated!!!
Resistance is fut...  ***BZZZRT***  THUD!!!
[General Protection Fault in MSBorg32.DLL]
Please contact the vendor of this Borg for more information
_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com

- ------------------------------

Date: Sat, 22 May 1999 22:15:28 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     if (cond)
>         exec sql ....
>     else
>         exec sql...
> 
>     Yes, this MUST be for right run as there:
> 
>     if (cond)
>     {
>         exec sql...
>     }
>     else
>     {
>         exec sql ...
>     }

This looks like a bug. I will check it asap.

Michael
- - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

End of pgsql-interfaces-digest V1 #355
**************************************

------------------------------

Date: Sun, 23 May 1999 10:00:15 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] What to use to get number of tuples in a query

On Fri, May 21, 1999 at 02:51:10PM -0700, Hitesh Patel wrote:
> What should I use to get the number of tuples returned by a PQexec()? 
> PQntuples seems to be doing the job but i'm not sure if that is the
> right thing to use.

At least that's the command I use with ecpg. :-)

However, if you're executing commands that do not return tuples you have to
use PQcmdTuples().

Michael
- -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

Date: Sun, 23 May 1999 11:12:31 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     So, why this brackets ('{' and '}') doesn't include ECPG? It may include
> this brackets before and after every 'EXEC SQL' command...

Okay, I'm working on this. BTW Oracle's PRO*C doesn't do this. :-) 

What's the current status of the code freeze. I take it I'm not allowed to
commit this change, am I?

Michael
- -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

End of pgsql-interfaces-digest V1 #356
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-05-24 04:28 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-05-24 04:28 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #356

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest      Sunday, May 23 1999      Volume 01 : Number 356



Index:

Undeliverable Message
Re: [INTERFACES] What to use to get number of tuples in a query
Re: [INTERFACES] ECPG feature

----------------------------------------------------------------------

Date: Sun, 23 May 99 5:27:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #355

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Saturday, May 22 1999     Volume 01 : Number 355



Index:

ECPG feature
jdbc - getArray
jdbc - number of updated rows
Error with JDBC
Re: [INTERFACES] ECPG feature

- ----------------------------------------------------------------------

Date: Fri, 21 May 1999 21:53:08 +0200
From: "Pavel PaJaSoft Janousek" <janousek@fonet.cz>
Subject: ECPG feature

    Hi,

    ECPG is very powerfull, I have one idea..

    If I have contruction ala:

    if (cond)
        exec sql ....
    else
        exec sql...

    Yes, this MUST be for right run as there:

    if (cond)
    {
        exec sql...
    }
    else
    {
        exec sql ...
    }

    So, why this brackets ('{' and '}') doesn't include ECPG? It may include
this brackets before and after every 'EXEC SQL' command...

    I know, that this is some modifications in output of parser... may
anybody do this modifications?

- - -------------------------------------------------------------------------
Pavel Janousek (PaJaSoft)                         FoNet, spol. s r. o.
Vyvoj software, sprava siti, Unix, Web, Y2K     Anenska 11, 602 00  Brno
E-mail: mailto:Janousek@FoNet.Cz                Tel.: +420  5  4324 4749
SMS:    mailto:P.Janousek@SMS.Paegas.Cz         Fax.: +420  5  4324 4751
WWW:    http://WWW.FoNet.Cz/                  E-mail: mailto:Info@FoNet.Cz
- - --------------------------------------------------------------------------

- ------------------------------

Date: Sat, 22 May 1999 12:24:28 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - getArray

Is there any working implementation of getArray? When it is
expected to be implemented in JDBC interface?


PS. I'm new this list, so if answers to my questions are in any kind
of faqs or were answered recently, please give a link to it.

PS2. I was trying to search archive-list, but it seems to be not
working...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- ------------------------------

Date: Sat, 22 May 1999 12:35:10 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - number of updated rows

Please tell me how to get to know how many rows has method
executeUpdate affected. According to documentation
<cut>
Returns:
        either the row count for INSERT, UPDATE or DELETE ...
</cut>
this method should return number of updated rows, but it always
returns 1. It's a feature(bug) of postgresql jdbc-driver?

The only solution for my problem, that I made up is:

turn off auto-commit

select count(*) from table
where tID
- - -- now i (probably)know number of updated rows

update table set ...
where tID

commit

turn on auto-commit
- - -- stupid, isn't it ...

PS. remember that I'm new here...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- ------------------------------

Date: Sat, 22 May 1999 04:36:47 -0700 (PDT)
From: Peter Garner <peter_garner@yahoo.com>
Subject: Error with JDBC

Hi All

I am using Postgres 6.5b and the JDBC that came with
it.   Under RH6.0 I get the following error attempting
to connect :

java.sql.SQLException: Something unusual has occured
to cause the driver to fail. Please report this
exception: java.sql.SQLException: Unknown Response
Type: K
	at postgresql.Driver.connect(Driver.java:106)
	at
java.sql.DriverManager.getConnection(DriverManager.java:83)
	at
java.sql.DriverManager.getConnection(DriverManager.java:126)
	at
crazy.pete.jnews.nntp.NewsReader.connectDBMS(NewsReader.java:95)
	at NewsMain.main(NewsMain.java:64)

I suspect this is something to do with a network
service not being properly started.  (I doubt it has
anything to do with the postmaster, since I am using
the identical startup script that worked with RH5.2.)
Oh, BTW both postmaster and the JDBC CLIENT are
running
on the same machine.  What service could I have
forgotten to start that is preventing TCP sockets from
working?   Thanks!
Peace,
Peter

We are Microsoft of Borg, you will be assimilated!!!
Resistance is fut...  ***BZZZRT***  THUD!!!
[General Protection Fault in MSBorg32.DLL]
Please contact the vendor of this Borg for more information
_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com

- ------------------------------

Date: Sat, 22 May 1999 22:15:28 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     if (cond)
>         exec sql ....
>     else
>         exec sql...
> 
>     Yes, this MUST be for right run as there:
> 
>     if (cond)
>     {
>         exec sql...
>     }
>     else
>     {
>         exec sql ...
>     }

This looks like a bug. I will check it asap.

Michael
- - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

End of pgsql-interfaces-digest V1 #355
**************************************

------------------------------

Date: Sun, 23 May 1999 10:00:15 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] What to use to get number of tuples in a query

On Fri, May 21, 1999 at 02:51:10PM -0700, Hitesh Patel wrote:
> What should I use to get the number of tuples returned by a PQexec()? 
> PQntuples seems to be doing the job but i'm not sure if that is the
> right thing to use.

At least that's the command I use with ecpg. :-)

However, if you're executing commands that do not return tuples you have to
use PQcmdTuples().

Michael
- -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

Date: Sun, 23 May 1999 11:12:31 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     So, why this brackets ('{' and '}') doesn't include ECPG? It may include
> this brackets before and after every 'EXEC SQL' command...

Okay, I'm working on this. BTW Oracle's PRO*C doesn't do this. :-) 

What's the current status of the code freeze. I take it I'm not allowed to
commit this change, am I?

Michael
- -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

------------------------------

End of pgsql-interfaces-digest V1 #356
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-05-25 07:21 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-05-25 07:21 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #357

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest      Monday, May 24 1999      Volume 01 : Number 357



Index:

Undeliverable Message
Undeliverable Message
[none]
Re: [GENERAL] Problems with INSERT INTO?
Re: [INTERFACES] ECPG feature
JDBC getQuote Call
ODBC with VISUAL BASIC applications to access POSTGRESQL db on LINUX??
JDBC to remote site
dynamic IPs
ODBC to access POSTGRESQL on LINUX - take 2
dynamic IPs
[INTERFACES] MSAccess problem deleting rows
Re: [INTERFACES] dynamic IPs 

----------------------------------------------------------------------

Date: Mon, 24 May 99 5:28:54 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #356

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest      Sunday, May 23 1999      Volume 01 : Number 356



Index:

Undeliverable Message
Re: [INTERFACES] What to use to get number of tuples in a query
Re: [INTERFACES] ECPG feature

- ----------------------------------------------------------------------

Date: Sun, 23 May 99 5:27:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #355

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Saturday, May 22 1999     Volume 01 : Number 355



Index:

ECPG feature
jdbc - getArray
jdbc - number of updated rows
Error with JDBC
Re: [INTERFACES] ECPG feature

- - ----------------------------------------------------------------------

Date: Fri, 21 May 1999 21:53:08 +0200
From: "Pavel PaJaSoft Janousek" <janousek@fonet.cz>
Subject: ECPG feature

    Hi,

    ECPG is very powerfull, I have one idea..

    If I have contruction ala:

    if (cond)
        exec sql ....
    else
        exec sql...

    Yes, this MUST be for right run as there:

    if (cond)
    {
        exec sql...
    }
    else
    {
        exec sql ...
    }

    So, why this brackets ('{' and '}') doesn't include ECPG? It may include
this brackets before and after every 'EXEC SQL' command...

    I know, that this is some modifications in output of parser... may
anybody do this modifications?

- - - -------------------------------------------------------------------------
Pavel Janousek (PaJaSoft)                         FoNet, spol. s r. o.
Vyvoj software, sprava siti, Unix, Web, Y2K     Anenska 11, 602 00  Brno
E-mail: mailto:Janousek@FoNet.Cz                Tel.: +420  5  4324 4749
SMS:    mailto:P.Janousek@SMS.Paegas.Cz         Fax.: +420  5  4324 4751
WWW:    http://WWW.FoNet.Cz/                  E-mail: mailto:Info@FoNet.Cz
- - - --------------------------------------------------------------------------

- - ------------------------------

Date: Sat, 22 May 1999 12:24:28 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - getArray

Is there any working implementation of getArray? When it is
expected to be implemented in JDBC interface?


PS. I'm new this list, so if answers to my questions are in any kind
of faqs or were answered recently, please give a link to it.

PS2. I was trying to search archive-list, but it seems to be not
working...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- - ------------------------------

Date: Sat, 22 May 1999 12:35:10 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - number of updated rows

Please tell me how to get to know how many rows has method
executeUpdate affected. According to documentation
<cut>
Returns:
        either the row count for INSERT, UPDATE or DELETE ...
</cut>
this method should return number of updated rows, but it always
returns 1. It's a feature(bug) of postgresql jdbc-driver?

The only solution for my problem, that I made up is:

turn off auto-commit

select count(*) from table
where tID
- - - -- now i (probably)know number of updated rows

update table set ...
where tID

commit

turn on auto-commit
- - - -- stupid, isn't it ...

PS. remember that I'm new here...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- - ------------------------------

Date: Sat, 22 May 1999 04:36:47 -0700 (PDT)
From: Peter Garner <peter_garner@yahoo.com>
Subject: Error with JDBC

Hi All

I am using Postgres 6.5b and the JDBC that came with
it.   Under RH6.0 I get the following error attempting
to connect :

java.sql.SQLException: Something unusual has occured
to cause the driver to fail. Please report this
exception: java.sql.SQLException: Unknown Response
Type: K
	at postgresql.Driver.connect(Driver.java:106)
	at
java.sql.DriverManager.getConnection(DriverManager.java:83)
	at
java.sql.DriverManager.getConnection(DriverManager.java:126)
	at
crazy.pete.jnews.nntp.NewsReader.connectDBMS(NewsReader.java:95)
	at NewsMain.main(NewsMain.java:64)

I suspect this is something to do with a network
service not being properly started.  (I doubt it has
anything to do with the postmaster, since I am using
the identical startup script that worked with RH5.2.)
Oh, BTW both postmaster and the JDBC CLIENT are
running
on the same machine.  What service could I have
forgotten to start that is preventing TCP sockets from
working?   Thanks!
Peace,
Peter

We are Microsoft of Borg, you will be assimilated!!!
Resistance is fut...  ***BZZZRT***  THUD!!!
[General Protection Fault in MSBorg32.DLL]
Please contact the vendor of this Borg for more information
_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com

- - ------------------------------

Date: Sat, 22 May 1999 22:15:28 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     if (cond)
>         exec sql ....
>     else
>         exec sql...
> 
>     Yes, this MUST be for right run as there:
> 
>     if (cond)
>     {
>         exec sql...
>     }
>     else
>     {
>         exec sql ...
>     }

This looks like a bug. I will check it asap.

Michael
- - - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- - ------------------------------

End of pgsql-interfaces-digest V1 #355
**************************************

- ------------------------------

Date: Sun, 23 May 1999 10:00:15 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] What to use to get number of tuples in a query

On Fri, May 21, 1999 at 02:51:10PM -0700, Hitesh Patel wrote:
> What should I use to get the number of tuples returned by a PQexec()? 
> PQntuples seems to be doing the job but i'm not sure if that is the
> right thing to use.

At least that's the command I use with ecpg. :-)

However, if you're executing commands that do not return tuples you have to
use PQcmdTuples().

Michael
- - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

Date: Sun, 23 May 1999 11:12:31 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     So, why this brackets ('{' and '}') doesn't include ECPG? It may include
> this brackets before and after every 'EXEC SQL' command...

Okay, I'm working on this. BTW Oracle's PRO*C doesn't do this. :-) 

What's the current status of the code freeze. I take it I'm not allowed to
commit this change, am I?

Michael
- - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

End of pgsql-interfaces-digest V1 #356
**************************************

------------------------------

Date: Mon, 24 May 99 5:28:59 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #356

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest      Sunday, May 23 1999      Volume 01 : Number 356



Index:

Undeliverable Message
Re: [INTERFACES] What to use to get number of tuples in a query
Re: [INTERFACES] ECPG feature

- ----------------------------------------------------------------------

Date: Sun, 23 May 99 5:27:05 +0100
From: <MAILER-DAEMON@mail1.sfr.fr>
Subject: Undeliverable Message

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #355

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

- - ----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Saturday, May 22 1999     Volume 01 : Number 355



Index:

ECPG feature
jdbc - getArray
jdbc - number of updated rows
Error with JDBC
Re: [INTERFACES] ECPG feature

- - ----------------------------------------------------------------------

Date: Fri, 21 May 1999 21:53:08 +0200
From: "Pavel PaJaSoft Janousek" <janousek@fonet.cz>
Subject: ECPG feature

    Hi,

    ECPG is very powerfull, I have one idea..

    If I have contruction ala:

    if (cond)
        exec sql ....
    else
        exec sql...

    Yes, this MUST be for right run as there:

    if (cond)
    {
        exec sql...
    }
    else
    {
        exec sql ...
    }

    So, why this brackets ('{' and '}') doesn't include ECPG? It may include
this brackets before and after every 'EXEC SQL' command...

    I know, that this is some modifications in output of parser... may
anybody do this modifications?

- - - -------------------------------------------------------------------------
Pavel Janousek (PaJaSoft)                         FoNet, spol. s r. o.
Vyvoj software, sprava siti, Unix, Web, Y2K     Anenska 11, 602 00  Brno
E-mail: mailto:Janousek@FoNet.Cz                Tel.: +420  5  4324 4749
SMS:    mailto:P.Janousek@SMS.Paegas.Cz         Fax.: +420  5  4324 4751
WWW:    http://WWW.FoNet.Cz/                  E-mail: mailto:Info@FoNet.Cz
- - - --------------------------------------------------------------------------

- - ------------------------------

Date: Sat, 22 May 1999 12:24:28 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - getArray

Is there any working implementation of getArray? When it is
expected to be implemented in JDBC interface?


PS. I'm new this list, so if answers to my questions are in any kind
of faqs or were answered recently, please give a link to it.

PS2. I was trying to search archive-list, but it seems to be not
working...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- - ------------------------------

Date: Sat, 22 May 1999 12:35:10 +0200
From: Piotr Stelmaszyk <kelman@fanthom.math.put.poznan.pl>
Subject: jdbc - number of updated rows

Please tell me how to get to know how many rows has method
executeUpdate affected. According to documentation
<cut>
Returns:
        either the row count for INSERT, UPDATE or DELETE ...
</cut>
this method should return number of updated rows, but it always
returns 1. It's a feature(bug) of postgresql jdbc-driver?

The only solution for my problem, that I made up is:

turn off auto-commit

select count(*) from table
where tID
- - - -- now i (probably)know number of updated rows

update table set ...
where tID

commit

turn on auto-commit
- - - -- stupid, isn't it ...

PS. remember that I'm new here...

/--------------------------------------------------------/
/- Piotr Stelmaszyk |---- Student of Computer Science ---/
/------------------ | at Poznan University of Technology /
/----- mailto:kelman@fanthom.math.put.poznan.pl ---------/
/----- mailto:kelman@alpha.net.pl -----------------------/
/--------------------------------------------------------/

- - ------------------------------

Date: Sat, 22 May 1999 04:36:47 -0700 (PDT)
From: Peter Garner <peter_garner@yahoo.com>
Subject: Error with JDBC

Hi All

I am using Postgres 6.5b and the JDBC that came with
it.   Under RH6.0 I get the following error attempting
to connect :

java.sql.SQLException: Something unusual has occured
to cause the driver to fail. Please report this
exception: java.sql.SQLException: Unknown Response
Type: K
	at postgresql.Driver.connect(Driver.java:106)
	at
java.sql.DriverManager.getConnection(DriverManager.java:83)
	at
java.sql.DriverManager.getConnection(DriverManager.java:126)
	at
crazy.pete.jnews.nntp.NewsReader.connectDBMS(NewsReader.java:95)
	at NewsMain.main(NewsMain.java:64)

I suspect this is something to do with a network
service not being properly started.  (I doubt it has
anything to do with the postmaster, since I am using
the identical startup script that worked with RH5.2.)
Oh, BTW both postmaster and the JDBC CLIENT are
running
on the same machine.  What service could I have
forgotten to start that is preventing TCP sockets from
working?   Thanks!
Peace,
Peter

We are Microsoft of Borg, you will be assimilated!!!
Resistance is fut...  ***BZZZRT***  THUD!!!
[General Protection Fault in MSBorg32.DLL]
Please contact the vendor of this Borg for more information
_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com

- - ------------------------------

Date: Sat, 22 May 1999 22:15:28 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     if (cond)
>         exec sql ....
>     else
>         exec sql...
> 
>     Yes, this MUST be for right run as there:
> 
>     if (cond)
>     {
>         exec sql...
>     }
>     else
>     {
>         exec sql ...
>     }

This looks like a bug. I will check it asap.

Michael
- - - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- - ------------------------------

End of pgsql-interfaces-digest V1 #355
**************************************

- ------------------------------

Date: Sun, 23 May 1999 10:00:15 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] What to use to get number of tuples in a query

On Fri, May 21, 1999 at 02:51:10PM -0700, Hitesh Patel wrote:
> What should I use to get the number of tuples returned by a PQexec()? 
> PQntuples seems to be doing the job but i'm not sure if that is the
> right thing to use.

At least that's the command I use with ecpg. :-)

However, if you're executing commands that do not return tuples you have to
use PQcmdTuples().

Michael
- - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

Date: Sun, 23 May 1999 11:12:31 +0200
From: Michael Meskes <meskes@postgresql.org>
Subject: Re: [INTERFACES] ECPG feature

On Fri, May 21, 1999 at 09:53:08PM +0200, Pavel PaJaSoft Janousek wrote:
>     So, why this brackets ('{' and '}') doesn't include ECPG? It may include
> this brackets before and after every 'EXEC SQL' command...

Okay, I'm working on this. BTW Oracle's PRO*C doesn't do this. :-) 

What's the current status of the code freeze. I take it I'm not allowed to
commit this change, am I?

Michael
- - -- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael.Meskes@gmx.net          | Use PostgreSQL!

- ------------------------------

End of pgsql-interfaces-digest V1 #356
**************************************

------------------------------

Date: Sun, 23 May 1999 23:30:16 -0500 (CDT)
From: mike longtine <longtine@uswest.net>
Subject: [none]

subscribe

------------------------------

Date: Mon, 24 May 1999 12:46:18 +0300
From: Herouth Maoz <herouth@oumail.openu.ac.il>
Subject: Re: [GENERAL] Problems with INSERT INTO?

At 12:22 +0300 on 24/05/1999, Anna Langer wrote:


> We are not really sure if this question is right for this mailinglist.
> We have some problem with INSERT INTO and we dont know how to solve it.We
> are writing it in a C-program. We are trying to get an integer from a file
> and put it into a database. And we are sure that we get a interger into our
> program.

The proper mailing list is the "interfaces" list, where I am redirecting
this post now.

> int aP0;
>
> PQexec(conn, "INSERT INTO octets VALUES(a)");
>
>
> But the program works when we do like this:
>
> PQexec(conn, "INSERT INTO octets VALUES(500)");
>
>
> It feels like we need to convert int a in some way, byt we dont know how. We
> are beginners with Postgresql.

This is less on the PostgreSQL side, and more on the C side. Just putting
"a" in a string doesn't tell C to pass the variable a. It just passes the
character "a", right?

What you have to do is pass the value of a as part of the command string.
So you have to make a string out of a. This is usually done with sprintf,
like this:

char command[1000];
int aP0;

sprintf( command, "INSERT INTO octets VALUES(%d)", a );

PQexec( conn, command );

Herouth

- --
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma

------------------------------

Date: Mon, 24 May 1999 14:16:28 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
Subject: Re: [INTERFACES] ECPG feature

> What's the current status of the code freeze. I take it I'm not allowed to
> commit this change, am I?

Sure, bug fixes are accepted at (almost) any time. Not sure what the
status of other stuff is, but I'm going to need some MVCC writeups for
the docs, and will need time to integrate them. There are a few other
bugs being chased, so I'm guessing that June 1 may slip a bit.

                      - Thomas

- -- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California

------------------------------

Date: Mon, 24 May 1999 10:18:24 -0400
From: Edwin Ramirez <ramirez@doc.mssm.edu>
Subject: JDBC getQuote Call

Hello,

I am using the postgresql JDBC driver with a reporting application,
which calls getQuote.  It seems that getQuote is not defined in the JDBC
driver.  

Does anybody know what this is supposed to do? 

- -Edwin S. Ramirez-

------------------------------

Date: Mon, 24 May 1999 11:56:05 -0400
From: "Justin Long" <justinlong@mail.strategicnetwork.org>
Subject: ODBC with VISUAL BASIC applications to access POSTGRESQL db on LINUX??

Ok, I'm confused... I've read most of the messages in my archives that deal
with PGSQL, ODBC... I would like to develop some applications using VB6 to
access PGSQL databases on Linux remotely over the Internet. Can someone
point me to an ODBC driver that would enable this? Should I use P. Harvey's
driver, or something else... what is postODBC? iODBC? I don't find any
references on the PGSQL web site and can't find other web sites that would
have these. Suggestions welcome!

Thanks,
Justin Long


Never retreat. Never surrender. Never cut a deal with a dragon.
_______________________________________________________________
Justin Long                   CIO / Site Editor
616 Station Square Ct         Network for Strategic Missions
Chesapeake, VA 23320          977 Centerville Trnpk CSB 317
JustinLong@xc.org             Va Beach, VA 23463
Check out our site at:        http://www.strategicnetwork.org

------------------------------

Date: Mon, 24 May 1999 11:54:22 -0400
From: Alex Turner <aturner@maaco.com>
Subject: JDBC to remote site

Help!

I have tried and tried, but I can't seem to connect to postgres through
JDBC from a remote site.

Could someone please send me a working pg_hba.conf file and a working
piece of JDBC?

TIA

Alex T

------------------------------

Date: Mon, 24 May 1999 13:31:33 -0400
From: "Michael R. Anderson" <andersmr@oscar.wvsc.edu>
Subject: dynamic IPs

May 24, 1999

I'd like to connect to a database from a machine that gets a new IP number every time it connects to the ISP.  How do I set up the pg_hba.conf file to allow this? 

Regards,

Mike Anderson

- --------------------------------------------------------------------------------------------------
Dr. Michael R. Anderson
Math Dept.
West Virginia State College
Institute, WV 25112

------------------------------

Date: Mon, 24 May 1999 15:19:26 -0400
From: "Justin Long" <justinlong@mail.strategicnetwork.org>
Subject: ODBC to access POSTGRESQL on LINUX - take 2

I was directed to the psqlODBC driver and have downloaded that and installed
it. Now I am attempting to access my Postgresql database on Linux using the
latest version (6.5) of PGSQL.

Here's the error log:

conn0083196, SQLDriverConnect( in)fDriverCompletion
Global Options: Versionunknown_sizes
x_varchar_size%4, max_longvarchar_size90
                disable_optimizer, unique_index
use_declarefetch
                text_as_longvarchars_longvarchar
bools_as_char
                extra_systable_prefixesCONN ERROR: funcerrmsg            ------------------------------------------------------------
            henv1129732, conn0083196, status6
            sock1129748, stmts1129788, lobj_type            ---------------- Socket Info -------------------------------
            socketto remote socket.'
            buffer_in0089524, buffer_out0093624
            buffer_filled_inuffer_filled_outuffer_read_in

I am using Visual Interdev 6 at the moment to attain a connection. Any
suggestions from the peanut gallery as to why it can't connect? (There isn't
a driver on the Linux side that one has to install, is there?)

Any suggestions, rotten fruit, eggs, whatever, welcome...

Justin Long


Never retreat. Never surrender. Never cut a deal with a dragon.
_______________________________________________________________
Justin Long                   CIO / Site Editor
616 Station Square Ct         Network for Strategic Missions
Chesapeake, VA 23320          977 Centerville Trnpk CSB 317
JustinLong@xc.org             Va Beach, VA 23463
Check out our site at:        http://www.strategicnetwork.org

------------------------------

Date: Mon, 24 May 1999 16:11:44 -0400
From: "Michael R. Anderson" <mike@ferrar.wvsc.edu>
Subject: dynamic IPs

May 24, 1999

I'd like to connect to a database from a machine that gets a new IP number every time it connects to the ISP.  How do I set up the pg_hba.conf file to allow this? 

Regards,

Mike Anderson

------------------------------

Date: Tue, 25 May 1999 00:55:22 +0200
From: leif@danmos.dk
Subject: [INTERFACES] MSAccess problem deleting rows

   Hello,

    I have a problem running M$Access on a PostgreSQL database,
deleting rows from 'raw' Access, i.e. doing an open on a table
selecting a hole row and then deleting this row. The problem
arises when the table includes a float:

create table effektivitet
  (
    id serial ,
    value float,
    primary key (id) 
  );
create unique index ix_effekt_uniq on effektivitet (id);

    Consider a row with the following values:
id  |  value
5   |  1.1666666666666666666....

Depending on how wide my float column is displayed, M$Access will
do something like: 'DELETE FROM effektivitet WHERE id value displays some (stupid) message like "Others have been changing ...."
and aborts the operation. This also goes for an update on such a
table. I can of course manually delete the row by doing a
'delete from effektivitet where id within Access or directly on the Linux box.

   This also happens with following piece of VB code:

Set rstEffective With rstEffective
    .Edit
    !Value     .Update
End With


   How can I make M$Acess use the unique index column for pointing
out this specific row in stead of generating a where clause containing
all fields in the table?

I am running PostgreSQL 6.4.2 on RedHat 5.0 and kernel 2.0.32. (I
downloaded and installed it just a few weeks ago. This goes for
psqlODBC as well).


    Greetings,

  Leif
  (leif@danmos.dk)

------------------------------

Date: Mon, 24 May 1999 20:11:49 -0400
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] dynamic IPs 

"Michael R. Anderson" <mike@ferrar.wvsc.edu> writes:
> I'd like to connect to a database from a machine that gets a new IP
> number every time it connects to the ISP.  How do I set up the
> pg_hba.conf file to allow this?

I think your only alternative is to find out the range of IP numbers
your ISP might assign (it's probably not large, one C block at most)
and then configure pg_hba.conf to allow access from any address in
that range.  For example, if the ISP says 12.34.56.0 - 12.34.56.255,
then you'd put something like

host         all        12.34.56.0  255.255.255.0      password

I'd recommend using an authentication method other than "trust" ;-)

			regards, tom lane

------------------------------

End of pgsql-interfaces-digest V1 #357
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread

* Undeliverable Message
@ 1999-07-09 04:24 MAILER-DAEMON@mail1.sfr.fr
  0 siblings, 0 replies; 30+ messages in thread

From: MAILER-DAEMON@mail1.sfr.fr @ 1999-07-09 04:24 UTC (permalink / raw)
  To: pgsql-interfaces@hub.org

To:            ISMTP@SFRA0046@Servers[<pgsql-interfaces-digest@hub.org>]
Cc:            
Subject:       pgsql-interfaces-digest V1 #411

Message not delivered to recipients below.  Press F1 for help with VNM
error codes.               

	VNM3043:  DE_VOLDER Fabrice@ATR_EXPL_LYON1@SFR_DO_CNTR_EST



VNM3043 -- MAILBOX IS FULL

   The message cannot be delivered because the
   recipient's mailbox contains the maximum number of 
   messages, as set by the system administrator.  The
   recipient must delete some messages before any
   other messages can be delivered.
    The maximum message limit for a user's mailbox is 
   10,000.  The default message limit is 1000 messages.  
   Administrators can set message limits using the 
   Mailbox  Settings function available in the 
   Manage User menu  (MUSER). 

   When a user's mailbox reaches the limit, the 
   user must delete some of the messages before 
   the mailbox can accept any more incoming messages.

----------------------  Original Message Follows  ----------------------


pgsql-interfaces-digest     Thursday, July 8 1999     Volume 01 : Number 411



Index:

[INTERFACES] JDBC escape problem
RE: [INTERFACES] JDBC escape problem
Libpq and Borland C++ Builder 4
RE: [INTERFACES] Libpq and Borland C++ Builder 4
RE: [INTERFACES] Libpq and Borland C++ Builder 4
java and postgresql 6.5
java in postgresql 65
libpq AND C++ Builder
No suitable driver
transactions in libpq++ require new connection? 
Postgresql + lo
Re: [INTERFACES] libpq AND C++ Builder
NEW WEB INTERFACE for PostgreSQL
Re: [INTERFACES] Postgresql + lo 
Re: [INTERFACES] transactions in libpq++ require new connection? 

----------------------------------------------------------------------

Date: Thu, 08 Jul 1999 00:56:51 -0700
From: Rolland Crunk <rc@aenet.net>
Subject: [INTERFACES] JDBC escape problem

I'm encountering a problem with the implementation of escapes using
the 6.5 JDBC driver.  If I attempt to insert a timestamp value using
the following syntax, I get an error from the postgreSQL parser complaining
about the '{' character:

  stmt.executeUpdate("insert into tstest values ( { ts '1999-07-07 00:00:00' } )");

However, the following statement works:

  stmt.executeUpdate("insert into tstest values ( '{ ts 1999-07-07 00:00:00 }' )");

Unfortunately, the former is the correct syntax where the second isn't.

From what I could determine tracing the code, there is no escape processing
performed in the PostgreSQL jdbc driver, and the error is originating from the
database backend.

I thought it unusual that I didn't see reference to this problem in the mail
archives (though I admit I only went back a few months).  Is this a known
problem?  

What are the consequences of fixing it in the back-end?  Will it break other 
drivers that depend on this syntax?  

Any advise would be appreciated.

Thanks in advance,

rc

------------------------------

Date: Thu, 8 Jul 1999 09:34:53 +0100 
From: Peter Mount <petermount@it.maidstone.gov.uk>
Subject: RE: [INTERFACES] JDBC escape problem

This is probably caused by the fact that currently we don't parse
anything within the JDBC driver. I'll put it on my todo list for 6.6.

- -----Original Message-----
From: Rolland Crunk [mailto:rc@aenet.net]
Sent: 08 July 1999 08:57
To: pgsql-interfaces@hub.org
Subject: [INTERFACES] JDBC escape problem




I'm encountering a problem with the implementation of escapes using
the 6.5 JDBC driver.  If I attempt to insert a timestamp value using
the following syntax, I get an error from the postgreSQL parser
complaining
about the '{' character:

  stmt.executeUpdate("insert into tstest values ( { ts '1999-07-07
00:00:00' } )");

However, the following statement works:

  stmt.executeUpdate("insert into tstest values ( '{ ts 1999-07-07
00:00:00 }' )");

Unfortunately, the former is the correct syntax where the second isn't.

From what I could determine tracing the code, there is no escape
processing
performed in the PostgreSQL jdbc driver, and the error is originating
from the
database backend.

I thought it unusual that I didn't see reference to this problem in the
mail
archives (though I admit I only went back a few months).  Is this a
known
problem?  

What are the consequences of fixing it in the back-end?  Will it break
other 
drivers that depend on this syntax?  

Any advise would be appreciated.

Thanks in advance,

rc

------------------------------

Date: Thu, 08 Jul 1999 11:22:49 +0200
From: Jean-Christophe FABRE <fabrejc@ensam.inra.fr>
Subject: Libpq and Borland C++ Builder 4

Hi!

When I try to use the libpq.lib (from the win32 psql.exe interface tool)
library with BC++ Builder, I get a message : LIBPQ.LIB contains invalid
OMF record, type 0x21 (possibly COFF).

First of all, what are OMF and COFF ?

I've found a tool (in C++Builder bin directory) to convert COFF2OMF, but
it didn't work.

Does anybody has a re-compiled libpq.lib which works fine with
C++Builder 4 ?

Please help!

Thanks

JC.Fabre

------------------------------

Date: Thu, 8 Jul 1999 11:31:47 +0200 
From: "Ansley, Michael" <Michael.Ansley@intec.co.za>
Subject: RE: [INTERFACES] Libpq and Borland C++ Builder 4

Welcome to the world of Win32.  There are several different object formats
when you are compiling under Win32.  It would appear that this error is
caused by your linker expecting one type when it actually gets another.
There may be an option somewhere to adjust your linker settings to cope with
a different object format.
This is a problem that is generally not experienced under UNIX, because
there is only one object format (that I'm aware of).

I'm not sure why you rconversion tool is not working, though, I suggest
getting hold of Inprise.


MikeA


>> When I try to use the libpq.lib (from the win32 psql.exe 
>> interface tool)
>> library with BC++ Builder, I get a message : LIBPQ.LIB 
>> contains invalid
>> OMF record, type 0x21 (possibly COFF).
>> 
>> First of all, what are OMF and COFF ?
>> 
>> I've found a tool (in C++Builder bin directory) to convert 
>> COFF2OMF, but
>> it didn't work.
>> 
>> Does anybody has a re-compiled libpq.lib which works fine with
>> C++Builder 4 ?
>> 
>> Please help!
>> 
>> Thanks
>> 
>> JC.Fabre
>> 
>> 

------------------------------

Date: Thu, 8 Jul 1999 13:13:57 +0200 
From: "Ansley, Michael" <Michael.Ansley@intec.co.za>
Subject: RE: [INTERFACES] Libpq and Borland C++ Builder 4

Perhaps you should just get hold of the Win32 source, and compile the entire
library again.  This would probably be the easiest solution.  I think that
the format that it is in is what VC++ uses.  I seem to remember trying it
out a while back.  However, if you get the source code, it shouldn't be a
problem to compile it.
>> 
>> Welcome to the world of Win32.  There are several different 
>> object formats
>> when you are compiling under Win32.  It would appear that 
>> this error is
>> caused by your linker expecting one type when it actually 
>> gets another.
>> There may be an option somewhere to adjust your linker 
>> settings to cope with
>> a different object format.
>> This is a problem that is generally not experienced under 
>> UNIX, because
>> there is only one object format (that I'm aware of).
>> 
>> I'm not sure why you rconversion tool is not working, 
>> though, I suggest
>> getting hold of Inprise.
>> 
>> 
>> MikeA
>> 
>> 
>> >> When I try to use the libpq.lib (from the win32 psql.exe 
>> >> interface tool)
>> >> library with BC++ Builder, I get a message : LIBPQ.LIB 
>> >> contains invalid
>> >> OMF record, type 0x21 (possibly COFF).
>> >> 
>> >> First of all, what are OMF and COFF ?
>> >> 
>> >> I've found a tool (in C++Builder bin directory) to convert 
>> >> COFF2OMF, but
>> >> it didn't work.
>> >> 
>> >> Does anybody has a re-compiled libpq.lib which works fine with
>> >> C++Builder 4 ?
>> >> 
>> >> Please help!
>> >> 
>> >> Thanks
>> >> 
>> >> JC.Fabre
>> >> 
>> >> 
>> 

------------------------------

Date: Thu, 8 Jul 1999 15:32:20 +0200 (CEST)
From: <yves@vlaanderen.net>
Subject: java and postgresql 6.5

I've been upgrading postgresql 6.4.2 to 6.5. It seems like the jdbc driver
included with postgres 65 doesn't work correctly:

 java.lang.IllegalArgumentException: Argument # > Arg length

or am i doing something wrong ?

- -Yves

On Fri, 14 May 1999, Alf Lewerken wrote:

> Hi all
> 
> I have the following problem:
> I'm using libpq++ to acces a Postgres-Database.
> 
> The table was created in psql using:
> create table test values (nr int4, some_value float4[]);
> 
> in my C++-program a piece of code is:
> 
> main()
> {
>   char *nr_string, *some_other_string;
> 
>   PgDatabase test(pgenv, "test");
>   test.Exec("begin");
>   test.Exec("declare c cursor for select * from test");
>   
>   for(int ist.Tuples();i++)
>   {
>      nr_string > 
>      some_other_string >      // PQgetvalue: ERROR! field number -1 is out of range
>    
>      // so how do I obtain values in some_value[1], some_value[2] .... ?
>   }
> }
> 
> any help would be appreciated.
> 
> 
> bye
> 
> 
> Alf Lewerken
> 

First, they ignore you.
Then they laugh at you.
Then they fight you.
Then you win.
              -- M. Ghandi

------------------------------

Date: Thu, 8 Jul 1999 15:40:16 +0200 (CEST)
From: <yves@vlaanderen.net>
Subject: java in postgresql 65

I've been upgrading postgresql 6.4.2 to 6.5. It seems like the jdbc driver
included with postgres 65 doesn't work correctly:
 
  java.lang.IllegalArgumentException: Argument # > Arg length
 
or am i doing something wrong ?
 
 -Yves

First, they ignore you.
Then they laugh at you.
Then they fight you.
Then you win.
              -- M. Ghandi

------------------------------

Date: Thu, 08 Jul 1999 16:00:43 +0200
From: Jean-Christophe FABRE <fabrejc@ensam.inra.fr>
Subject: libpq AND C++ Builder

Does anybody have a libpq.lib (or libpq++.lib) win32 version which works
fine with Borland C++ builder 4, or know where I can find it.

I tried to re-compile it with C++B4, but no luck.

The version which comes with the psql.exe distribution doesn't work
either.

Thanks

JC

------------------------------

Date: Thu, 08 Jul 1999 11:38:24 -0400
From: "C.J. Pena" <cjp@professionalmedia.com>
Subject: No suitable driver

Hello,
I am using the Postgre v6.5-JDK11 driver (also tried the Postgre v6.4
driver) and
I receive "No suitable driver" error when I try to establish a
connection.
The registration -- Class.forname('postgresql.Driver') -- executes Ok.
This error leads me to believe the problem is in driver setup; if I
received something like
"connection refused" I would look first at security, say in pg_hba.conf,
right?
Thank you.

------------------------------

Date: Thu, 8 Jul 1999 15:55:59 -0400 (EDT)
From: George Young <gry@ll.mit.edu>
Subject: transactions in libpq++ require new connection? 

I am using libpq++ with gcc egcs-2.91.66 (egcs-1.1.2 release) on RH linux 5.1
with Postgres 6.5.  I need to use transactions to maintain consistency
when an application's logical operation actually updates multiple tables.

Currently, the PgTransaction class only has a public constructor which
opens a new connection to the DB, and closes it on commit.  For an application
making many short transactions, in an environment with many active clients,
this seems to be very wasteful of network and cpu resources.  Is there some
reason a PgTransaction could not be constructed from an existing PgDatabase
(or PgConnection)?  Maybe trans should be a lightweight class to avoid
problems with inheriting from PgDatabase and thus having to deal with 
copy/reference-count etc. problems?

I know I can roll my own by just Exec("begin"), etc, but having the
transaction *committed* (not conn closed) in the destructor would be very
handy.


Also, there's no rollback member...


On yet another note, it would be much neater if the c++ interface would use
'string' type for text args and returns.  I'm tired of writing foo.c_str()
everywhere...


Thanks,
	George

[I'm not too experienced with c++, so I *welcome* any comments/suggestions]


George Young,  Rm. L-204		gry@ll.mit.edu
MIT Lincoln Laboratory
244 Wood St.
Lexington, Massachusetts  02420-9108	(781) 981-2756

------------------------------

Date: Fri, 9 Jul 1999 00:19:51 +0200
From: Florian Baumert <baumert@plt.de>
Subject: Postgresql + lo

Hi there,

I have a major problem with postgresql 6.5. In my database, I've
created the lo-type, as explained in the FAQ. I have a table which
uses this type. If i want to acces it with (eg) perl
      use Pg; $conn The xinv33025 exists and the oid 33025 was created by a call to lo_create.

What happens is that it writes a -1 to the screen and a database-error "ERROR: lo_lseek: invalid large obj descriptor (0)"
The same happens, if I use php3 (compiled against postgresql) and the
ODBC-driver for windoes (06.40.0006). If i compile and start
examples/test/lotest.c (hope, it's the right name) in the
posrgresql-src directory, it works!!!

If I comment out the call to lo_lseek in lo_open, it works further,
but then I get problems in lo_close (same error as above, only in
lo_close).

What happens here?

Thanx in advance

      Florian


                      \\|||//
                      |     |
                      (.) (.)
! Florian Baumert                                       !
? Birkenweg 2                                           ?
! D-61267 Neu-Anspach                                   ?
! Tel.:06081-9 63 63 7                                  !
? ! baumert@plt.de                             www.plt.de !

------------------------------

Date: Thu, 8 Jul 1999 18:25:13 -0400 (EDT)
From: "Geoffrey C. Speicher" <geoff@sirius.trassociates.com>
Subject: Re: [INTERFACES] libpq AND C++ Builder

> Does anybody have a libpq.lib (or libpq++.lib) win32 version which works
> fine with Borland C++ builder 4, or know where I can find it.

Any reason you don't want to use ODBC with BCB4?  Grab the driver from
http://www.insightdist.com/psqlodbc/ and set up a System DSN; all the BCB
data-aware components work just swell with it ... don't forget to check
"recognize unique indexes" in the advanced driver settings, or it will
probably crash on you like it did for me.

Or did you want to implement native versions of the components for
PostgreSQL?  :)

Geoff

------------------------------

Date: Thu, 8 Jul 1999 14:39:49 -0400 (EDT)
From: seb@Panther4095.eiu.edu
Subject: NEW WEB INTERFACE for PostgreSQL

Hi all,

sorry if get this mail 2 or 3 times!

I am working on a CGI (perl) to access ANY postgres DB 
from the web: "PGase"

Here are the main features:

_ Login page to enter the CGI (default guest OK!).

_ Select/Insert/Update/Delete with just the mouse. 
    (foreign keys are links to primary key table!)

_ Import/Export data from/to flat .txt files 
   
_ UPLOAD SQL scripts from IMPORT to create database structure
   directly from the CGI, or put data back from a pg_dump.

_ Administration also through a CREATE (SQL commands) page.

_ little HELP... :)

_ build queries dynamically (point & click: basic but OK 
   even when referential integrity between 2 tables).

_ run perfect with LYNX!!!

_ record queries 
_ Pie CHARTs on a selected field in a table.


Still to do:

_ FIND functions to get any records having "$string" 
   in one of its fields...  or between dates...

_ IP control access from the CGI.

_ few bugs to correct

_ move to mod_perl

_ lots of other ideas, like BLOBS, personalized forms...

Do you like the CGI?
What would you change?
What would you like to see?
Feel free to give me any advices!
'Say that's for the PostgreSQL community!  ;)

Thanks for your help,
Have fun,
                                Sebastien.

Oups, maybe you need this:
http://panther4095.eiu.edu/PGase

The code:
http://math.eiu.edu/seb/cgi-bin/pg
                                                
._...... _...._...._...._...._..._ ......_
|.|.....(_)..|.\..|.|..|.|..|.|..\.\..././ Sebastien Flacher
|.|.....|.|..|..\.|.|..|.|..|.|...\.\././
|.|.....|.|..|...\|.|..|.|..|.|..../._.\   phone: 217.345.8874
|.|___..|.|..|.|\...|..|.|__|.|..././.\.\  email: seb@math.eiu.edu
|_____).|_| .|_|.\__|..|______|../_/...\_\ web site: math.eiu.edu/seb

------------------------------

Date: Thu, 08 Jul 1999 21:16:14 -0400
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] Postgresql + lo 

Florian Baumert <baumert@plt.de> writes:
> What happens is that it writes a -1 to the screen and a database-error "ERROR: lo_lseek: invalid large obj descriptor (0)"

This needs to go into the FAQ, I think, 'cause you're about the third
person to ask the same question in the past couple weeks.

You need to wrap a transaction ("begin" ... "commit") around any use
of a large object handle, ie any lo_open ... lo_close sequence.

This requirement has always been in the LO docs, but Postgres 6.5 is the
first release that enforces the rule (by closing all open LO handles at
end of statement, if not within a transaction).  In prior versions,
you could sometimes get away with not using a transaction, but it
was NOT reliable.

			regards, tom lane

------------------------------

Date: Thu, 08 Jul 1999 21:20:58 -0400
From: Tom Lane <tgl@sss.pgh.pa.us> 
Subject: Re: [INTERFACES] transactions in libpq++ require new connection? 

George Young <gry@ll.mit.edu> writes:
> Currently, the PgTransaction class only has a public constructor which
> opens a new connection to the DB, and closes it on commit.

Ugh.  I agree that's pretty awful.

> I know I can roll my own by just Exec("begin"), etc, but having the
> transaction *committed* (not conn closed) in the destructor would be very
> handy.
> Also, there's no rollback member...

Actually, I think the cleanest design would be to have a commit() member
function.  If the object is destroyed without having committed, the
default behavior ought to be to abort (rollback), not commit.  The
reason I think this is that if you imagine a PgTransaction object that
is local to a function, and the function is exited by an exception,
you probably want abort to happen rather than commit.

There might be some cases where you'd rather it worked the other way
around --- if so, we could have a constructor option to set the default
behavior at destruct time.  But I think defaulting to abort would be the
safest behavior for a program that uses exceptions.

			regards, tom lane

------------------------------

End of pgsql-interfaces-digest V1 #411
**************************************





^ permalink  raw  reply  [nested|flat] 30+ messages in thread


end of thread, other threads:[~1999-07-09 04:24 UTC | newest]

Thread overview: 30+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-02-12 08:08 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-02-12 09:18 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-02 22:25 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-02 23:10 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 02:12 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 03:19 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 04:09 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 04:34 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 04:40 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 05:06 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 05:35 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 05:58 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 06:32 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 07:15 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-03 07:48 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 02:43 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 03:34 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 04:18 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 04:44 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 05:06 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 05:30 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 05:48 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 06:16 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 06:39 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-03-25 07:15 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-05-23 04:27 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-05-24 04:28 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-05-24 04:28 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-05-25 07:21 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr
1999-07-09 04:24 Undeliverable Message MAILER-DAEMON@mail1.sfr.fr

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox