Undeliverable Message - Mailing list pgsql-interfaces
| From | |
|---|---|
| Subject | Undeliverable Message |
| Date | |
| Msg-id | vines.n4,8+J4CrqA@SFRA0046. Whole thread Raw |
| List | pgsql-interfaces |
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
errorat 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
forthe 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_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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
doesnot exist.'
STATEMENT ERROR: func - ------------------------------------------------------------
hdbc3237224, stmt3550944, result
manual_resultparernal
bindings indings_allocated
parameters
rameters_allocated
statement_type
tement stmt_with_params data_at_exec currTuple
maxRowst_size yset_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_out uffer_read_inB
conn3237224, query [ fetched 920 rows ]
conn3632808, SQLDriverConnect( in)DSN info: DSN readonly conn_settings
translation_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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_longvarchar ools_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_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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:
Permissiondenied.'
STATEMENT ERROR: func - ------------------------------------------------------------
hdbc3944104, stmt3950776, result
manual_resultparernal
bindings indings_allocated
parameters
rameters_allocated
statement_type
tement stmt_with_params data_at_exec currTuple
maxRowst_size yset_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_out uffer_read_in@
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN readonly conn_settings
translation_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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:
Permissiondenied.'
STATEMENT ERROR: func - ------------------------------------------------------------
hdbc3944104, stmt3950776, result
manual_resultparernal
bindings indings_allocated
parameters
rameters_allocated
statement_type
tement stmt_with_params data_at_exec currTuple
maxRowst_size yset_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_out uffer_read_inA
conn3944104, SQLDisconnect
conn3632808, query [ fetched 1 rows ]
conn3944104, SQLDriverConnect( in)DSN info: DSN readonly conn_settings
translation_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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:
Permissiondenied.'
STATEMENT ERROR: func - ------------------------------------------------------------
hdbc3944104, stmt3950776, result
manual_resultparernal
bindings indings_allocated
parameters
rameters_allocated
statement_type
tement stmt_with_params data_at_exec currTuple
maxRowst_size yset_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_out uffer_read_inA
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN readonly conn_settings
translation_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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:
Permissiondenied.'
STATEMENT ERROR: func - ------------------------------------------------------------
hdbc3944104, stmt3950776, result
manual_resultparernal
bindings indings_allocated
parameters
rameters_allocated
statement_type
tement stmt_with_params data_at_exec currTuple
maxRowst_size yset_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_out uffer_read_inE
conn3944104, SQLDisconnect
conn3944104, SQLDriverConnect( in)DSN info: DSN readonly conn_settings
translation_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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:
Permissiondenied.'
STATEMENT ERROR: func - ------------------------------------------------------------
hdbc3944104, stmt3950776, result
manual_resultparernal
bindings indings_allocated
parameters
rameters_allocated
statement_type
tement stmt_with_params data_at_exec currTuple
maxRowst_size yset_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_out uffer_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
bindings indings_allocated
parameters3645616, parameters_allocated
statement_type
tement stmt_with_params data_at_exec currTuple
maxRowst_size yset_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_out uffer_read_inH
conn3944104, SQLDriverConnect( in)DSN info: DSN readonly conn_settings
translation_dllGlobalOptions: Version disable_optimizer, unique_index_declarefetch
text_as_longvarchars_longvarchar ools_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;PWDWVERSIONINGMTABLES ONNSETTINGS
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
**************************************
pgsql-interfaces by date: