pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedError Message
7+ messages / 5 participants
[nested] [flat]
* Error Message
@ 1998-10-22 17:49 Gregory W Burnham <gburnham@sfu.ca>
1998-10-23 01:52 ` Re: [INTERFACES] Error Message Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 7+ messages in thread
From: Gregory W Burnham @ 1998-10-22 17:49 UTC (permalink / raw)
To: pgsql-interfaces
I'm getting the error:
FATAL 1: Socket command type
But I can't find any referance to it anywhere. This is for an INSERT
query and the result returned from PQexec is NULL.
Any pointers?
Gregory W Burnham
Software Engineer
Excite Labs
Simon Fraser University
Vancouver, BC
604 291 3615 ph
604 291 5679 fx
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [INTERFACES] Error Message
1998-10-22 17:49 Error Message Gregory W Burnham <gburnham@sfu.ca>
@ 1998-10-23 01:52 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 1998-10-23 01:52 UTC (permalink / raw)
To: Gregory W Burnham <gburnham@sfu.ca>; +Cc: pgsql-interfaces
"Gregory W Burnham" <gburnham@sfu.ca> writes:
> I'm getting the error:
> FATAL 1: Socket command type
> But I can't find any referance to it anywhere. This is for an INSERT
> query and the result returned from PQexec is NULL.
This is coming out of src/backend/tcop/postgres.c; it looks like the
backend got a NULL character at the point where it expected to read
the first byte of a new command string from the frontend.
My guess is that the frontend and backend got out of sync. The easiest
way to make that happen is to mess up a COPY IN or COPY OUT sequence,
but it could also be that you have a broken frontend that's sending
garbage.
What frontend software are you using, anyway? And what version?
What were you doing *before* the command on which you noticed the
failure?
regards, tom lane
^ permalink raw reply [nested|flat] 7+ messages in thread
* error message
@ 1999-05-03 18:03 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-05-04 12:41 ` Re: [INTERFACES] error message José Soares <jose@sferacarta.com>
0 siblings, 1 reply; 7+ messages in thread
From: JT Kirkpatrick @ 1999-05-03 18:03 UTC (permalink / raw)
To: 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>
hi, i'm using access97 linked to postgres(6.4.2) tables through the new
v.6.4 odbc. i can open a form, it shows me data for an initial record, and
then bombs. here is the message in the log file -- i can't figure out why
it is bombing. does anyone have a clue?? do those "-" or "/" in various
"vinvnum" fields cause problems?? it shows valid data first, waits for a
second, and then bombs!
TIA, jt
conn=50745568, query='declare SQL_CUR0308FC60 cursor for SELECT
"vnum","vinvnum","vinvrecdt","vinvduedt","vinvamt","glnum","checkdt","ch
ecknum","ponum",'#S_C_H#' FROM "ap" WHERE "vnum" = 20000 AND "vinvnum" =
'13639 VOID' OR "vnum" = 20000 AND "vinvnum" = '138577-Void' OR "vnum" =
20000 AND "vinvnum" = '142185-SHOP' OR "vnum" = 20000 AND "vinvnum" =
'2Brother Credit 1/99' OR "vnum" = 20000 AND "vinvnum" = '37003 OFO-Chairs'
OR "vnum" = 20000 AND "vinvnum" = 'Aberdene, SD' OR "vnum" = 20000 AND
"vinvnum" = 'Adj for Nov' OR "vnum" = 20000 AND "vinvnum" = 'Adj for Oct
97' OR "vnum" = 20000 AND "vinvnum" = 'Agson 132289' OR "vnum" = 20000 AND
"vinvnum" = 'Air Trans''
ERROR from backend during send_query: 'ERROR: Unable to find an ordering
operator '<' for type unknown.
Use an explicit ordering operator or modify the query.'
conn=50745568, query='ABORT'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while
executing the query'
--------------------------------------------------------
----
hdbc=50745568, stmt=50920544, result=0
manual_result=0, prepare=1, internal=0
bindings=0, bindings_allocated=0
parameters=50911028, parameters_allocated=20
statement_type=0, statement='SELECT
"vnum","vinvnum","vinvrecdt","vinvduedt","vinvamt","glnum","checkdt","ch
ecknum","ponum",'#S_C_H#' FROM "ap" WHERE "vnum" = ? AND "vinvnum" = ? OR
"vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ?
AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND
"vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum" =
? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ?'
stmt_with_params='declare SQL_CUR0308FC60 cursor for
SELECT
"vnum","vinvnum","vinvrecdt","vinvduedt","vinvamt","glnum","checkdt","ch
ecknum","ponum",'#S_C_H#' FROM "ap" WHERE "vnum" = 20000 AND "vinvnum" =
'13639 VOID' OR "vnum" = 20000 AND "vinvnum" = '138577-Void' OR "vnum" =
20000 AND "vinvnum" = '142185-SHOP' OR "vnum" = 20000 AND "vinvnum" =
'2Brother Credit 1/99' OR "vnum" = 20000 AND "vinvnum" = '37003 OFO-Chairs'
OR "vnum" = 20000 AND "vinvnum" = 'Aberdene, SD' OR "vnum" = 20000 AND
"vinvnum" = 'Adj for Nov' OR "vnum" = 20000 AND "vinvnum" = 'Adj for Oct
97' OR "vnum" = 20000 AND "vinvnum" = 'Agson 132289' OR "vnum" = 20000 AND
"vinvnum" = 'Air Trans''
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_CUR0308FC60'
----------------QResult Info
-------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR: Unable to
find an ordering operator '<' for type unknown.
Use an explicit ordering operator or modify the query.'
------------------------------------------------------------
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [INTERFACES] error message
1999-05-03 18:03 error message JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
@ 1999-05-04 12:41 ` José Soares <jose@sferacarta.com>
0 siblings, 0 replies; 7+ messages in thread
From: José Soares @ 1999-05-04 12:41 UTC (permalink / raw)
To: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>; hackers <pgsql-hackers@postgresql.org>
JT Kirkpatrick ha scritto:
> hi, i'm using access97 linked to postgres(6.4.2) tables through the new
> v.6.4 odbc. i can open a form, it shows me data for an initial record, and
> then bombs. here is the message in the log file -- i can't figure out why
> it is bombing. does anyone have a clue?? do those "-" or "/" in various
> "vinvnum" fields cause problems?? it shows valid data first, waits for a
> second, and then bombs!
>
I had a similar error when I tried to order retrieved data by a field not in
the table or a calculated field.
Seems that Access request an order by a field with an unknown type.
I can emulate a similar message as:
select 'AAAAAA' union select 'ZZZZZZ' order by 1 asc;
ERROR: Unable to identify a binary operator '>' for types unknown and unknown
select 'aaaaaa' union select 'zzzzzz' order by 1;
ERROR: Unable to identify a binary operator '<' for types unknown and unknown
May be we need a default for UNKNOWN types (what do you think Thomas, if we
make unknown type = text type?)
Any way. Try these functions:
create function unknown_lt(unknown,unknown) returns bool as
'declare
i1 text;
i2 text;
begin
i1:= $1;
i2:= $2;
return (i1 < i2);
end; ' language 'plpgsql';
CREATE
create operator < (
leftarg=unknown,
rightarg=unknown,
procedure=unknown_lt,
commutator='<',
negator='>=',
restrict=eqsel,
join=eqjoinsel
);
CREATE
create function unknown_gt(unknown,unknown) returns bool as
'declare
i1 text;
i2 text;
begin
i1:= $1;
i2:= $2;
return (i1 > i2);
end; ' language 'plpgsql';
CREATE
create operator > (
leftarg=unknown,
rightarg=unknown,
procedure=unknown_gt,
commutator='>',
negator='<=',
restrict=eqsel,
join=eqjoinsel
);
CREATE
select 'AAAAAA' union select 'ZZZZZZ' order by 1 asc;
?column?
--------
AAAAAA
ZZZZZZ
(2 rows)
select 'aaaaaa' union select 'zzzzzz' order by 1 desc;
?column?
--------
zzzzzz
aaaaaa
(2 rows)
EOF
______________________________________________________________
PostgreSQL 6.5.0 on i586-pc-linux-gnu, compiled by gcc 2.7.2.3
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jose'
^ permalink raw reply [nested|flat] 7+ messages in thread
* RE: [INTERFACES] error message
@ 1999-05-03 19:38 Michael J Davis <michael.j.davis@tvguide.com>
0 siblings, 0 replies; 7+ messages in thread
From: Michael J Davis @ 1999-05-03 19:38 UTC (permalink / raw)
To: 'JT Kirkpatrick' <jt-kirkpatrick@mpsllc.com>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>
How was the select statement created? It does not look like anything Access
created. Access likes to surround the items in the where clause with (),
lots of (). Have you tried executing this select statement directly in
psql?
> -----Original Message-----
> From: JT Kirkpatrick [SMTP:jt-kirkpatrick@mpsllc.com]
> Sent: Monday, May 03, 1999 12:03 PM
> To: 'pgsql-interfaces@hub.org'
> Subject: [INTERFACES] error message
>
> hi, i'm using access97 linked to postgres(6.4.2) tables through the new
> v.6.4 odbc. i can open a form, it shows me data for an initial record,
> and
> then bombs. here is the message in the log file -- i can't figure out why
>
> it is bombing. does anyone have a clue?? do those "-" or "/" in various
> "vinvnum" fields cause problems?? it shows valid data first, waits for a
> second, and then bombs!
>
> TIA, jt
>
> conn=50745568, query='declare SQL_CUR0308FC60 cursor for SELECT
> "vnum","vinvnum","vinvrecdt","vinvduedt","vinvamt","glnum","checkdt","ch
> ecknum","ponum",'#S_C_H#' FROM "ap" WHERE "vnum" = 20000 AND "vinvnum" =
>
> '13639 VOID' OR "vnum" = 20000 AND "vinvnum" = '138577-Void' OR "vnum" =
> 20000 AND "vinvnum" = '142185-SHOP' OR "vnum" = 20000 AND "vinvnum" =
> '2Brother Credit 1/99' OR "vnum" = 20000 AND "vinvnum" = '37003
> OFO-Chairs'
> OR "vnum" = 20000 AND "vinvnum" = 'Aberdene, SD' OR "vnum" = 20000 AND
> "vinvnum" = 'Adj for Nov' OR "vnum" = 20000 AND "vinvnum" = 'Adj for Oct
> 97' OR "vnum" = 20000 AND "vinvnum" = 'Agson 132289' OR "vnum" = 20000 AND
>
> "vinvnum" = 'Air Trans''
> ERROR from backend during send_query: 'ERROR: Unable to find an ordering
> operator '<' for type unknown.
> Use an explicit ordering operator or modify the query.'
> conn=50745568, query='ABORT'
> STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while
> executing the query'
>
> --------------------------------------------------------
> ----
> hdbc=50745568, stmt=50920544, result=0
> manual_result=0, prepare=1, internal=0
> bindings=0, bindings_allocated=0
> parameters=50911028, parameters_allocated=20
> statement_type=0, statement='SELECT
> "vnum","vinvnum","vinvrecdt","vinvduedt","vinvamt","glnum","checkdt","ch
> ecknum","ponum",'#S_C_H#' FROM "ap" WHERE "vnum" = ? AND "vinvnum" = ?
> OR
> "vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ?
>
> AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND
> "vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum"
> =
> ? OR "vnum" = ? AND "vinvnum" = ? OR "vnum" = ? AND "vinvnum" = ?'
> stmt_with_params='declare SQL_CUR0308FC60 cursor for
> SELECT
> "vnum","vinvnum","vinvrecdt","vinvduedt","vinvamt","glnum","checkdt","ch
> ecknum","ponum",'#S_C_H#' FROM "ap" WHERE "vnum" = 20000 AND "vinvnum" =
>
> '13639 VOID' OR "vnum" = 20000 AND "vinvnum" = '138577-Void' OR "vnum" =
> 20000 AND "vinvnum" = '142185-SHOP' OR "vnum" = 20000 AND "vinvnum" =
> '2Brother Credit 1/99' OR "vnum" = 20000 AND "vinvnum" = '37003
> OFO-Chairs'
> OR "vnum" = 20000 AND "vinvnum" = 'Aberdene, SD' OR "vnum" = 20000 AND
> "vinvnum" = 'Adj for Nov' OR "vnum" = 20000 AND "vinvnum" = 'Adj for Oct
> 97' OR "vnum" = 20000 AND "vinvnum" = 'Agson 132289' OR "vnum" = 20000 AND
>
> "vinvnum" = 'Air Trans''
> 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_CUR0308FC60'
> ----------------QResult Info
> -------------------------------
> CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR: Unable
> to
> find an ordering operator '<' for type unknown.
> Use an explicit ordering operator or modify the query.'
> ------------------------------------------------------------
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* RE: [INTERFACES] error message
@ 1999-05-04 15:37 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-05-05 13:32 ` Re: [HACKERS] RE: [INTERFACES] error message José Soares <jose@sferacarta.com>
0 siblings, 1 reply; 7+ messages in thread
From: JT Kirkpatrick @ 1999-05-04 15:37 UTC (permalink / raw)
To: 'Jose Soares' <jose@sferacarta.com>; hackers <pgsql-hackers@postgresql.org>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>
i do have a few fields (combo boxes based on a query) that sorted on a
calculated field -- but they seem to work fine in other forms. --don't
think that was it. but, based on your postulations i re-did a few of the
queries to NOT sort on the calculated fields. still bombed though. . .
so, i deleted the link to the particular table, and then re-linked to it,
and to my surprise, i can now pull up the form without it bombing. i can
even zip through all the records (36k of them) if i wish. but now it still
has a problem -- the recordset is not updateable. if i open the table
directly (not through any query, and again, from within access97, pgsql
6.4.2), the table itself is not updateable. the table DOES have a primary
key -- a DUAL FIELD primary key. I found over the last few weeks that
Access97 will treat any ODBC table without a primary key defined as not
updateable, but will it also do the same for DUAL FIELD primary key ODBC
tables?? it appears so, but can anyone confirm it??
jt
-----Original Message-----
From: Jose Soares [SMTP:jose@sferacarta.com]
Sent: Tuesday, May 04, 1999 8:42 AM
To: JT Kirkpatrick; hackers
Subject: Re: [INTERFACES] error message
JT Kirkpatrick ha scritto:
> hi, i'm using access97 linked to postgres(6.4.2) tables through the new
> v.6.4 odbc. i can open a form, it shows me data for an initial record,
and
> then bombs. here is the message in the log file -- i can't figure out
why
> it is bombing. does anyone have a clue?? do those "-" or "/" in various
> "vinvnum" fields cause problems?? it shows valid data first, waits for a
> second, and then bombs!
>
I had a similar error when I tried to order retrieved data by a field not
in
the table or a calculated field.
Seems that Access request an order by a field with an unknown type.
I can emulate a similar message as:
select 'AAAAAA' union select 'ZZZZZZ' order by 1 asc;
ERROR: Unable to identify a binary operator '>' for types unknown and
unknown
select 'aaaaaa' union select 'zzzzzz' order by 1;
ERROR: Unable to identify a binary operator '<' for types unknown and
unknown
May be we need a default for UNKNOWN types (what do you think Thomas, if we
make unknown type = text type?)
Any way. Try these functions:
create function unknown_lt(unknown,unknown) returns bool as
'declare
i1 text;
i2 text;
begin
i1:= $1;
i2:= $2;
return (i1 < i2);
end; ' language 'plpgsql';
CREATE
create operator < (
leftarg=unknown,
rightarg=unknown,
procedure=unknown_lt,
commutator='<',
negator='>=',
restrict=eqsel,
join=eqjoinsel
);
CREATE
create function unknown_gt(unknown,unknown) returns bool as
'declare
i1 text;
i2 text;
begin
i1:= $1;
i2:= $2;
return (i1 > i2);
end; ' language 'plpgsql';
CREATE
create operator > (
leftarg=unknown,
rightarg=unknown,
procedure=unknown_gt,
commutator='>',
negator='<=',
restrict=eqsel,
join=eqjoinsel
);
CREATE
select 'AAAAAA' union select 'ZZZZZZ' order by 1 asc;
?column?
--------
AAAAAA
ZZZZZZ
(2 rows)
select 'aaaaaa' union select 'zzzzzz' order by 1 desc;
?column?
--------
zzzzzz
aaaaaa
(2 rows)
EOF
______________________________________________________________
PostgreSQL 6.5.0 on i586-pc-linux-gnu, compiled by gcc 2.7.2.3
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jose'
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [HACKERS] RE: [INTERFACES] error message
1999-05-04 15:37 RE: [INTERFACES] error message JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
@ 1999-05-05 13:32 ` José Soares <jose@sferacarta.com>
0 siblings, 0 replies; 7+ messages in thread
From: José Soares @ 1999-05-05 13:32 UTC (permalink / raw)
To: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>; +Cc: psql-interfaces@hub.org'\" \" <pgsql-interfaces@hub.org>
JT Kirkpatrick ha scritto:
> i do have a few fields (combo boxes based on a query) that sorted on a
> calculated field -- but they seem to work fine in other forms. --don't
> think that was it. but, based on your postulations i re-did a few of the
> queries to NOT sort on the calculated fields. still bombed though. . .
> so, i deleted the link to the particular table, and then re-linked to it,
> and to my surprise, i can now pull up the form without it bombing. i can
> even zip through all the records (36k of them) if i wish. but now it still
> has a problem -- the recordset is not updateable. if i open the table
> directly (not through any query, and again, from within access97, pgsql
> 6.4.2), the table itself is not updateable. the table DOES have a primary
> key -- a DUAL FIELD primary key. I found over the last few weeks that
> Access97 will treat any ODBC table without a primary key defined as not
> updateable, but will it also do the same for DUAL FIELD primary key ODBC
> tables?? it appears so, but can anyone confirm it??
I'm using also access97 with postodbc 6.40.0005 and PostgreSQL v6.5beta1 and it
works fine and I have primary
keys like:
Table = figure_pkey
+----------------------------------+----------------------------------+-------+
| Field | Type | Length|
+----------------------------------+----------------------------------+-------+
| azienda | char() | 16 |
| tipo | char() | 2 |
| gruppo | int4 | 4 |
| inizio_attivita | date | 4 |
+----------------------------------+----------------------------------+-------+
Which version of psqlodbc are you using?
I know that Access uses dynaset or snapshots to connect to database.
- If you attach a table without define a primary key Access connects to the
table as snapshot and you can't write table.
- If you define a primary key then Access connects to the table as dynaset and
you are able to write table.
- You must define primary key during table linkage time.
- If you have the ODBC manager option RECOGNIZE UNIQUE INDEXES checked then you
don't need define it
because Access recognize the primary key automatically.
- If you have the ODBC manager option READ ONLY checked then all linked tables
are read only.
--
______________________________________________________________
PostgreSQL 6.5.0 on i586-pc-linux-gnu, compiled by gcc 2.7.2.3
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jose'
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~1999-05-05 13:32 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-10-22 17:49 Error Message Gregory W Burnham <gburnham@sfu.ca>
1998-10-23 01:52 ` Tom Lane <tgl@sss.pgh.pa.us>
1999-05-03 18:03 error message JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-05-04 12:41 ` Re: [INTERFACES] error message José Soares <jose@sferacarta.com>
1999-05-03 19:38 RE: [INTERFACES] error message Michael J Davis <michael.j.davis@tvguide.com>
1999-05-04 15:37 RE: [INTERFACES] error message JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-05-05 13:32 ` Re: [HACKERS] RE: [INTERFACES] error message José Soares <jose@sferacarta.com>
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