Skip site navigation (1) Skip section navigation (2)

[ psqlodbc-Bugs-1000467 ] Can't use (b)lobs with Omnis Studio v4

From: <noreply(at)pgfoundry(dot)org>
To: noreply(at)pgfoundry(dot)org
Subject: [ psqlodbc-Bugs-1000467 ] Can't use (b)lobs with Omnis Studio v4
Date: 2006-01-18 10:34:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Bugs item #1000467, was opened at 2005-12-07 13:23
You can respond by visiting:

Category: None
Group: None
>Status: Open
Resolution: Postponed
Priority: 3
Submitted By: Nobody (None)
Assigned to: Ludek Finstrle (luf)
Summary: Can't use (b)lobs with Omnis Studio v4

Initial Comment:

My company uses PGSQL v8.1 as backend database and Raining Data's Omnis Studio v4.1 as developpement tool (see There is a demo version).

LOB (blobs, clobs) can't be used with Postgresql and ODBC, either using lo or bytea. Queries fail or the app' crashes.

I tried different settings with psqlOBDC with no luck.

I've joined my log.

If you have questions or need more details : nte(at)mustinformatique(dot)fr 


Nathanael TERRIEN.


>Comment By: Dave Page  (dpage)
Date: 2006-01-18 10:34

Luf has been dealing with this off-tracker. Bug re-opened.


Comment By: Dave Page  (dpage)
Date: 2006-01-18 10:18

No response from reporter - bug deleted.


Comment By: Ludek Finstrle (luf)
Date: 2005-12-07 15:15

It seems to me that it's coming cutted to ODBC driver.
There is no source code of OStudio so I don't know why it is doing it this way. Maybe psqlODBC answer bad information before. But I don't know where and I don't know what OStudio expects.

How do you created lo type? Could you try newer ODBC driver? Could you post minimalistic example (or steps leads to reproduce it)? I don't want to learn OStudio.

I don't think that OStudio sent exactly the same query ;-)


Comment By: Must Informatique (mustinfodev)
Date: 2005-12-07 14:55

Sorry for the double post before.

Yes, I've read the logs.
You're right, of course, this isn't a correct SQL command and that's the real problem :)

The SQL commande seems to be "cut" and I don't why or by whom (Omnis Studio or the psqlODBC driver) ... but you should know ;).
ANd it's cut just before a blob datatype.
FYI, the exact same command sent by OStudio to MySQL 4.x through ODBC works perfectly and create a "mediumblob" field.

Those logs aside (wich result of an automated VCS Database creation monitored by OSTudio), I've never been able to use lo/bytea blobs with psqlODBC and Omnis Studio : it crash or read/write faulty data.

I have, of course, sent a bug report to Raining Data too but I thought I should inform the great psqlODBC team also ;)

Thanks for looking at this issue, regards,


Comment By: Ludek Finstrle (luf)
Date: 2005-12-07 14:04

I upload logs and delete second report ...


Comment By: Ludek Finstrle (luf)
Date: 2005-12-07 14:03

I see no problem with lo or bytea:
CREATE TABLE VCS_ComponentData (vcs_ID int4 NOT NULL,vcs_ChunkID int4 NULL,vcs_ChunkSize int4 NULL,vcs_ChunkChecksum int4 NULL,vcs_Data 

This isn't SQL command. Do you read what driver report?

STATEMENT ERROR: errnum=7, errmsg='Error while executing the query'
CONN ERROR: errnum=108, errmsg='ERROR:  syntax error at end of input au caractĨre 137'

Please don't create new bug report. Either log in before you report bug or send additional information to pgsql-odbc mailing list.


You can respond by visiting:

pgsql-odbc by date

Next:From: Dave PageDate: 2006-01-18 10:36:36
Subject: Re: Text for new bug-entry
Previous:From: Ludek FinstrleDate: 2006-01-18 10:31:39
Subject: Re: Text for new bug-entry

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group