Обсуждение: ColAttribute not implemented?
Hi everybody,
after some computing I found my psqlodbc filled with these errors (well,
after 10 minutes the psqlodbc log was more than 4 MB...):
CONN ERROR: func=PGAPI_ColAttributes, desc='', errnum=0, errmsg='(NULL)'
------------------------------------------------------------
henv=103876384, conn=103857648, status=1, num_stmts=16
sock=103876112, stmts=103876032, lobj_type=-999
---------------- Socket Info -------------------------------
socket=900, reverse=0, errornumber=0, errormsg='(NULL)'
buffer_in=103868584, buffer_out=117047360
buffer_filled_in=264, buffer_filled_out=0, buffer_read_in=264
STATEMENT ERROR: func=PGAPI_ColAttributes, desc='', errnum=28, errmsg='ColAttribute for this type not implemented yet'
------------------------------------------------------------
hdbc=103857648, stmt=103875360, result=103875808
manual_result=0, prepare=0, internal=0
bindings=103874672, bindings_allocated=4
parameters=0, parameters_allocated=0
statement_type=0, statement='SELECT * FROM "attributo" WHERE "idFSV" =1171'
stmt_with_params='SELECT * FROM "attributo" WHERE "idFSV" =1171'
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_CUR06310320'
----------------QResult Info -------------------------------
fields=103875776, manual_tuples=0, backend_tuples=117055568, tupleField=117055568, conn=103857648
fetch_count=0, fcount=7, num_fields=4, cursor='(NULL)'
message='(NULL)', command='SELECT', notice='(NULL)'
status=8, inTuples=0
The "attributo" table is (from PgAdminII definition pane):
CREATE TABLE "attributo" (
"nome" varchar(30) NOT NULL,
"idFSV" int4 NOT NULL,
"tipo" int2 NOT NULL,
"id_enum" int4,
CONSTRAINT "attributo_pkey" PRIMARY KEY ("nome", "idFSV"),
CONSTRAINT "<unnamed>" FOREIGN KEY ("id_enum") REFERENCES "enumerazione" ("id_enum") ON DELETE CASCADE ON UPDATE NO
ACTIONNOT DEFERRABLE INITIALLY IMMEDIATE,
CONSTRAINT "<unnamed>" FOREIGN KEY ("idFSV") REFERENCES "datoFSV" ("idFSV") ON DELETE CASCADE ON UPDATE NO ACTION NOT
DEFERRABLEINITIALLY IMMEDIATE
);
Mmm.... what can I do to stop this flooding of errors? I think that this could
harm performance even when psqlodbc log is turned off, isn't it?
I'm using Postgres 7.1.3 and driver version 07.01.0011 (that's what
I read from the psqlodbc log, at least...).
Best regards
Andrea Aime
BTW: I see the same error on other tables, that are using the
same datatypes as "attributo"
Andrea Aime wrote: > > Hi everybody, > after some computing I found my psqlodbc filled with these errors (well, > after 10 minutes the psqlodbc log was more than 4 MB...): > > CONN ERROR: func=PGAPI_ColAttributes, desc='', errnum=0, errmsg='(NULL)' > ------------------------------------------------------------ > henv=103876384, conn=103857648, status=1, num_stmts=16 > sock=103876112, stmts=103876032, lobj_type=-999 > ---------------- Socket Info ------------------------------- > socket=900, reverse=0, errornumber=0, errormsg='(NULL)' > buffer_in=103868584, buffer_out=117047360 > buffer_filled_in=264, buffer_filled_out=0, buffer_read_in=264 > STATEMENT ERROR: func=PGAPI_ColAttributes, desc='', errnum=28, errmsg='ColAttribute for this type not implemented yet' Could you send me the Mylog(Debug) output ? regards, Hiroshi Inoue
Hi Andrea, > -----Original Message----- > From: Andrea Aime [mailto:aaime@comune.modena.it] > Sent: Thursday, April 11, 2002 6:30 PM > To: Hiroshi Inoue > Subject: Re: [ODBC] ColAttribute not implemented? > > > Here it is, the smallest I could get (only 5 seconds of operation...) > but as far I can see, it has all the relevant errors... The errors you reported are all for non ODBC standard options(maybe for M$ SQL Server). There seems no way other than rejecting them. If the error log is a problem, I would suppress the logging for the options. regards, Hiroshi Inoue
Damn... of course I can turn off the logging, but it would be better if these non standard options would not be used at all... it seems even more strange to me, since the preferred way to connect to MS SQL server is to use ADO over OLE-DB... Does anyone knows how to turn off these weird options? Dave? Do you see the same problems with pgAdmin? I'm using ADO 2.6 Best regards Andrea Aime Hiroshi Inoue wrote: > > Hi Andrea, > > > -----Original Message----- > > From: Andrea Aime [mailto:aaime@comune.modena.it] > > Sent: Thursday, April 11, 2002 6:30 PM > > To: Hiroshi Inoue > > Subject: Re: [ODBC] ColAttribute not implemented? > > > > > > Here it is, the smallest I could get (only 5 seconds of operation...) > > but as far I can see, it has all the relevant errors... > > The errors you reported are all for non ODBC standard options(maybe > for M$ SQL Server). There seems no way other than rejecting them. > If the error log is a problem, I would suppress the logging for the > options. > > regards, > Hiroshi Inoue > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly
Andrea Aime wrote:
>
> Damn... of course I can turn off the logging, but it would
Probably I suppressed the error log messages you reported.
Please try the latest driver.
> be better if these non standard options would not be used
> at all... it seems even more strange to me, since the preferred
> way to connect to MS SQL server is to use ADO over OLE-DB...
> Does anyone knows how to turn off these weird options? Dave?
> Do you see the same problems with pgAdmin? I'm using ADO 2.6
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/