This is a discussion on =?UTF-8?B?WyBwc3Fsb2RiYy1CdWdzLTEwMDA0NjcgXSBDYW4ndCB1c2 UgKGIpbG9icyB3aXRoIE9tbmlzIFN0dWRpbyB2NA==?= within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> Bugs item #1000467, was opened at 07/12/2005 13:23 You can respond by visiting: http://pgfoundry.org/tracker/?func=d...oup_id=1000125 Category: None Group: None Status: ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Bugs item #1000467, was opened at 07/12/2005 13:23 You can respond by visiting: http://pgfoundry.org/tracker/?func=d...oup_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: Must Informatique (mustinfodev) Date: 07/12/2005 14: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/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, Nathanael. ---------------------------------------------------------------------- Comment By: Ludek Finstrle (luf) Date: 07/12/2005 14:04 Message: I upload logs and delete second report ... ---------------------------------------------------------------------- Comment By: Ludek Finstrle (luf) Date: 07/12/2005 14: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 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: http://pgfoundry.org/tracker/?func=d...oup_id=1000125 ---------------------------(end of broadcast)--------------------------- TIP 1: 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 |
| Thread Tools | |
| Display Modes | |
|
|