From: | Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com> |
---|---|
To: | Ben Ramsey <br(at)benandliz(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Adding long text to a text field generates an error |
Date: | 2004-01-19 23:02:03 |
Message-ID: | 20040119230203.70409.qmail@web20808.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
--- Ben Ramsey <br(at)benandliz(dot)com> wrote:
> > "Text" in this context refers to the PostgreSQL
> > datatype "text". Whether the setting matters
> depends
> > on whether "text" is what you are using, and on
> what
> > LongVarChar maps to in your environment. For
> example,
> > in MS Access it maps to "memo", which has
> limitations
> > (e.g. cannot be included in the where clause of a
> > query).
> >
> > I think better just to up the number. Pick a big
> > number, and see what happens. While you are at
> it, up
> > the Max VarChar setting, too.
>
> Well, I am using the PostgreSQL datatype "text" in
> this context, so that
> should work. Also, why should I raise Max VarChar
> over the default
> varchar setting of 255?
I guess it doesn't matter if you are using the text
datatype. AFAIK varchar(n) maps to ODBC VarChar, so
it would matter if you were using varchar(n).
>
> I guess what I'll do is just play around with it as
> someone suggested.
> I really didn't know those settings were there until
> you asked me to
> post the ODBC driver settings. I had completely
> overlooked them.
>
> Thanks a bunch!
We haven't established that this works, yet ;-)
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Ramsey | 2004-01-19 23:22:09 | Re: Adding long text to a text field generates an error |
Previous Message | Ben Ramsey | 2004-01-19 22:39:54 | Re: Adding long text to a text field generates an error |