Unix Technical Forum

[ psqlodbc-Bugs-1000744 ] 08.02.01: Incorrect size returned for adVarWChar and adVarChar fields after Paremeters.Refresh.

This is a discussion on [ psqlodbc-Bugs-1000744 ] 08.02.01: Incorrect size returned for adVarWChar and adVarChar fields after Paremeters.Refresh. within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> Bugs item #1000744, was opened at 2006-10-04 18:42 You can respond by visiting: http://pgfoundry.org/tracker/?func=d...oup_id=1000125 Category: None Group: None Status: ...


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > pgsql Interfaces odbc

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-16-2008, 03:09 AM
noreply@pgfoundry.org
 
Posts: n/a
Default [ psqlodbc-Bugs-1000744 ] 08.02.01: Incorrect size returned for adVarWChar and adVarChar fields after Paremeters.Refresh.

Bugs item #1000744, was opened at 2006-10-04 18:42
You can respond by visiting:
http://pgfoundry.org/tracker/?func=d...oup_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Adam Biser (adambiser)
Assigned to: Nobody (None)
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 is 254 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, I will provide it.

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

>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=d...oup_id=1000125

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 05:01 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com