[ psqlodbc-Bugs-1000778 ] Error 3219 - Operation is not allowed in this context - Blobs and VB6
am 16.11.2006 08:45:05 von noreplyBugs item #1000778, was opened at 2006-11-13 17:52
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=10007 78&group_id=1000125
Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 3
Submitted By: Nobody (None)
>Assigned to: Hiroshi Inoue (hinoue)
Summary: Error 3219 - Operation is not allowed in this context - Blobs and VB6
Initial Comment:
I am trying to use PostgreSQL 8.1.X, but now when I try retrieve a file in lo field type, occurs the erros Error 3219 - Operation is not allowed in this context, I am using Visual Basic 6 - ADO - ODBC 8.02.02
I did this example for test.
http://gborg.postgresql.org/project/psqlodbc/genpage.php?how to-vblo
------------------------------------------------------------ ----------
Comment By: Nobody (None)
Date: 2006-11-14 15:10
Message:
I could to solve this problem.
This error occurs because my odbc connection was configured with
protocol 6.4 because I am used to odbc 7.03.02, for the new version
the protocol must be 7.4.
Others configuration must be change is the Driver, that must be Postgresql ANSI
My connection String
Before:
Driver=PostgreSQL};SERVER=localhost;DATABASE=db;UID=postgres ;PWD=;ReadOnly=0;
Protocol=6.4;
FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;ShowSystemTab les=1;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;Max VarcharSize=254;MaxLongVarcharSize=65536;Debug=0;CommLog=0;O ptimizer=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;Unkn ownsAsLongVarchar=0;BoolsAsChar=0;Parse=0;CancelAsFreeStmt=0 ;ExtraSysTablePrefixes=dd_;;LFConversion=1;UpdatableCursors= 0;DisallowPremature=0;TrueIsMinus1=1;BI=-5;
After;
Driver={PostgreSQL ANSI};SERVER=localhost;PORT=5432;UID=postgres;PWD=;SSLmode=d isable;ReadOnly=0;
Protocol=7.4;
FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;ShowSystemTab les=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;Max VarcharSize=254;MaxLongVarcharSize=8190;Debug=0;CommLog=0;Op timizer=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;Unkno wnsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=0; ExtraSysTablePrefixes=dd_;;LFConversion=1;UpdatableCursors=1 ;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinar y=0;UseServerSidePrepare=0;LowerCaseIdentifier=0;XaOpt=1"
------------------------------------------------------------ ----------
Comment By: Nobody (None)
Date: 2006-11-14 14:53
Message:
Hi Hiroshi
Yes I defined the type lo and I have been use type lo since version 7.4..
Juari
------------------------------------------------------------ ----------
Comment By: Hiroshi Inoue (hinoue)
Date: 2006-11-14 02:45
Message:
Hi
Did you define the type lo and use it ?
regards,
Hiroshi Inoue
------------------------------------------------------------ ----------
Comment By: Nobody (None)
Date: 2006-11-14 00:33
Message:
Hi, My Apologize
I was post this question and after my test, I found the solution, this error occurs because my odbc connection was configured with protocol 6.4 because I am used to odbc 7.03.02, for the new version the protocol must be 7.4.
Thanks
Juari D. Silva
Developer Coordinator
------------------------------------------------------------ ----------
Comment By: Hiroshi Inoue (hinoue)
Date: 2006-11-13 23:45
Message:
Hi
Did you define the type lo and use it ?
regards,
Hiroshi Inoue
------------------------------------------------------------ ----------
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=10007 78&group_id=1000125
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org