[ psqlodbc-Bugs-1000744 ] 08.02.01: Incorrect size returned for adVarWChar and adVarChar fields after Paremeters.Refresh.
От | |
---|---|
Тема | [ psqlodbc-Bugs-1000744 ] 08.02.01: Incorrect size returned for adVarWChar and adVarChar fields after Paremeters.Refresh. |
Дата | |
Msg-id | 20061020035620.5D2D1216F10@pgfoundry.org обсуждение исходный текст |
Список | pgsql-odbc |
Bugs item #1000744, was opened at 2006-10-04 18:42 You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000744&group_id=1000125 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Adam Biser (adambiser) >Assigned to: Hiroshi Inoue (hinoue) Summary: 08.02.01: Incorrect size returned for adVarWChar and adVarChar fields after Paremeters.Refresh. Initial Comment: I'm using VB6 on a Windows XP machine with ODBC driver 08.02.01 and PostgreSQL 8.2beta1. CREATE TABLE testtable ( code integer NOT NULL, testfield character varying(5000), CONSTRAINT proschargemstrpk PRIMARY KEY (proschargecode) ) When I use a Command object, set the CommandText, and perform a .Parameters.Refresh, the .Size of testfield's parameter is254 instead of 5000 and setting the .Value of the parameter to anything longer than 254 characters results in an error. This happens with both the Unicode and ANSI drivers. The create table statement that pgAdmin III gives me is included at the top. If any additional information is needed, Iwill provide it. ---------------------------------------------------------------------- Comment By: Adam Biser (adambiser) Date: 2006-10-05 12:55 Message: Not really because the schema is written for an AS400, which doesn't have a TEXT data type. We're interested in having PostgreSQL as an alternative and I think that of the two work-arounds, setting the "Max Varchar Size" to a larger number is more acceptable at the moment. I'd rather do that than maintain two versions of the schema. Thanks ---------------------------------------------------------------------- Comment By: Hiroshi Inoue (hinoue) Date: 2006-10-05 02:30 Message: Unfortunately this problem is hard to solve. Couldn't you change the defintion of the textfiled from varchar(5000) to text ? regards, Hiroshi Inoue ---------------------------------------------------------------------- Comment By: Adam Biser (adambiser) Date: 2006-10-04 20:12 Message: I did find a work-around for this by change MaxVarcharSize to match the Max LongVarChar size, but I don't think the parameter should say it's a VarChar(254) when it's a LongVarChar(5000). The "Text as LongVarChar" checkbox has been checked on the DSN's property pages. ---------------------------------------------------------------------- Comment By: Adam Biser (adambiser) Date: 2006-10-04 18:54 Message: Sorry, the primary key should be "code"... I meant to simplify the field names, but forgot to change the constraint line. ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000744&group_id=1000125
В списке pgsql-odbc по дате отправления: