[unixODBC-dev] DB2 and datatype -350
Mike.Cowley at neonsys.com
Thu Aug 19 21:05:15 BST 2004
Sorry for delayed response, but I've been behind.
I hope you found this info already, but if not here it is.
The DB2 doc states :
-350 INVALID SPECIFICATION OF A LARGE OBJECT COLUMN
Explanation: The ALTER TABLE, CREATE TABLE, or CREATE INDEX statement is
invalid for one of the following reasons:
o A LOB column cannot be added to a temporary table.
o A LOB column cannot be added to a table defined with an EDITPROC.
o The PRIMARY KEY clause cannot specify a LOB column as a column of the
o The UNIQUE clause cannot specify a LOB column as a column of the
o The referential-constraint clause cannot specify a LOB column as a
column of a foreign key.
o The CREATE INDEX statement cannot name a LOB column as a column of the
o A LOB column cannot be specified in a references clause.
System Action: The statement cannot be executed.
Programmer Response: Correct the syntax and resubmit the statement.
From: unixodbc-dev-bounces at mail.easysoft.com
[mailto:unixodbc-dev-bounces at mail.easysoft.com]On Behalf Of Nick Gorham
Sent: Friday, August 06, 2004 7:13 AM
To: Development issues and topics for unixODBC
Subject: Re: [unixODBC-dev] DB2 and datatype -350
Daly, Fergal wrote:
> I'm trying to get something working with DB2 and unixODBC and after a
> lot of hassle it's mostly there but now I'm getting -350 for the data
> type when I do GetColumnDesc. Judging by the column type and some other
> stuff, it seems to be a Unicode clob/memo/ntext field. Is this correct?
> I can't find it in any headers (unixODBC, windows or DB2). Is it DB2
> specific? Thanks,
I would guess so.
unixODBC-dev mailing list
unixODBC-dev at mail.easysoft.com
More information about the unixODBC-dev