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

Bugs item #1000467, was opened at 2005-12-07 14:23
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000467&group_id=1000125

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:
Hi.

My company uses PGSQL v8.1 as backend database and Raining Data's Omnis Studio v4.1 as developpement tool (see
http://www.omnis.net/.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@mustinformatique.fr

Thanks.

Nathanael TERRIEN.


----------------------------------------------------------------------

>Comment By: Ludek Finstrle (luf)
Date: 2006-06-01 20:47

Message:
Could you send us the mylog output or better the minimalistic example which leads to error?
I have downloded Omnis studio but I see no help from you.

I'm looking forward

Luf

----------------------------------------------------------------------

Comment By: Must Informatique (mustinfodev)
Date: 2006-05-10 09:13

Message:
BLOBs still don't work correctly with version 08.02.0002.
Worse, through an ODBC connexion, Omnis Studio can't see anymore the tables and their structure, though it was working
withprevious version and querries seem to be still functionning. 
But we use to use the Unicode driver of the previous version and everything is coded with UTF8 on the DB server. Is is
related? 

----------------------------------------------------------------------

Comment By: Dave Page  (dpage)
Date: 2006-04-28 11:12

Message:
Please test version 08.02.0002 (available from http://pgfoundry.org/frs/?group_id=1000125) and report whether or not
theproblem still exists. 

----------------------------------------------------------------------

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

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

----------------------------------------------------------------------

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

Message:
No response from reporter - bug deleted.

----------------------------------------------------------------------

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

Message:
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
reproduceit)? 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 15:55

Message:
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/byteablobs 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,
Nathanael.



----------------------------------------------------------------------

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

Message:
I upload logs and delete second report ...

----------------------------------------------------------------------

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

Message:
I see no problem with lo or bytea:
[SQLExecute]
CREATE TABLE VCS_ComponentData (vcs_ID int4 NOT NULL,vcs_ChunkID int4 NULL,vcs_ChunkSize int4 NULL,vcs_ChunkChecksum
int4NULL,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
mailinglist. 

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000467&group_id=1000125