Re: [INTERFACES] Foreign Keys - Mailing list pgsql-interfaces

From Byron Nikolaidis
Subject Re: [INTERFACES] Foreign Keys
Date
Msg-id 36DC61D6.6DF4E87D@insightdist.com
Whole thread Raw
In response to RE: [INTERFACES] Foreign Keys  (Michael Davis <michael.davis@prevuenet.com>)
Responses Re: [INTERFACES] Foreign Keys  ("Gene Selkov Jr." <selkovjr@xnet.com>)
List pgsql-interfaces

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=admin.  You could probably set the uid to something more reasonable in your connect string
in Access.


conn=153944104, query='SELECT "logvalues"."id" FROM "logvalues" '
ERROR from backend during send_query: 'ERROR:  logvalues: Permission denied.'

conn=153944104, query='SELECT "memberid" ,"firstname" ,"lastname"  FROM "membership" ORDER BY
"lastname" ,"firstname"  '
ERROR from backend during send_query: 'ERROR:  membership: Permission denied.'

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.'

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.'

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'



The second problem is this:

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'


Since postgres will not recognize the syntax (where 'col' = null)...  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


pgsql-interfaces by date:

Previous
From:
Date:
Subject: Undeliverable Message
Next
From:
Date:
Subject: Undeliverable Message