From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | thiemo(at)gelassene-pferde(dot)biz, psycopg <psycopg(at)lists(dot)postgresql(dot)org> |
Subject: | Re: TypeError: dict is not a sequence |
Date: | 2024-11-01 16:12:13 |
Message-ID: | 99a9cec1-09a0-41fb-91b2-d153c4ccf5a4@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On 11/1/24 08:11, thiemo(at)gelassene-pferde(dot)biz wrote:
> Hi Jim
>
>> I suspect the source of the problem is the commented-out line
>>
>> -- ST_FromGDALRaster(pg_read_binary_file(%s)),
>>
>> in the statement.
>
> You are right. I was not expecting the comment to be relevant for the
> parameter replacement. Many thanks for the hint.
That is an SQL(---) comment and I am guessing the parser sees the
parameter before it gets to the comment.
>
> I now have an error, not related to psycopg, as far as I can tell.
>
> psycopg2.errors.InternalError_: RASTER_fromGDALRaster: Could not open
> bytea with GDAL. Check that the bytea is of a GDAL supported format
This looks to be on the PostGIS end related to the ST_FromGDALRaster()
function. Does:
select ST_FromGDALRaster(the_field);
work in psql?
>
>> Maybe the difference in the errors is due to a different version of
>> psycopg? This is what I am using:
>>
>>>>> sys.version
>>> '3.12.3 (main, Sep 11 2024, 14:17:37) [GCC 13.2.0]'
>>> >>> psycopg.__version__
>>> '3.2.3'
>
> Probably.
>>>> sys.version
> '3.11.2 (main, Aug 26 2024, 07:20:54) [GCC 12.2.0]'
>>>> psycopg.__version__
> '3.1.7'
>
>
> Many thanks for your support.
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | thiemo | 2024-11-01 16:49:05 | Re: TypeError: dict is not a sequence |
Previous Message | thiemo | 2024-11-01 15:11:13 | Re: TypeError: dict is not a sequence |