This is a multi-part message in MIME format.
------_=_NextPart_001_01C8B077.32113A00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The other disadvantage I have noticed is that you can't override operator
b=
ehavior of text but you can for varchar=2E=0D=0A =0D=0ASo I have been able
=
to override the case sensitivity of varchar fields (which is annoying when
=
working with MS Access etc) simply by changing the way LIKE, =3D > etc=2E
=
are handled for varchar=2E Since text is defined in pg_catalog, it
doesn'=
t seem possible to override it or at least haven't had any success with
tha=
t=2E Maybe I am missing something=2E=0D=0A
=0D=0AThanks,=0D=0ARegina=0D=0A=
=0D=0A=0D=0A________________________________=0D=0A=0D=0AFrom:
pgsql-novice=
-owner@[EMAIL PROTECTED]
on behalf of Greg Cocks=0D=0ASent: Wed 5/7/2008
1:4=
8 PM=0D=0ATo: PostgreSQL List - Novice=0D=0ASubject: Re: [NOVICE]
Disadvant=
ages to using "text"=0D=0A=0D=0A=0D=0A=0D=0AOne disadvantage is that if
you=
are using MS Access as a front-end via=0D=0AODBC / linked tables, you can
=
not do joins on fields set as text (in=0D=0Aqueries,
etc)=0D=0A=0D=0A=0D=0A=
-----Original Message-----=0D=0AFrom: Frank Bax
[mailto:fbax@[EMAIL PROTECTED]
Wednesday, May 07, 2008 10:55 AM=0D=0ATo: PostgreSQL List -
No=
vice=0D=0ASubject: Re: [NOVICE] Disadvantages to using
"text"=0D=0A=0D=0AAu=
rynn Shaw wrote:=0D=0A> Internally, Postgres treats a VARCHAR(n) as a TEXT
=
with a CHECK=0D=0A> constraint applied to it, so VARCHAR is going to be
sli=
ghtly slower to=0D=0Ause=2E=0D=0A=0D=0A=0D=0ADon't you mean VARCHAR(n)
will=
be slightly slower on UPDATES=2E=0D=0A=0D=0A--=0D=0ASent via pgsql-novice
=
mailing list (pgsql-novice@[EMAIL PROTECTED]
)=0D=0ATo make changes to your
s=
ubscription:=0D=0Ahttp://www=2Epostgresql=2Eorg/mailpref/pgsql-novice=0D=0A=
=0D=0A--=0D=0ASent via pgsql-novice mailing list (pgsql-novice@[EMAIL PROTECTED]
)=0D=0ATo make changes to your
subscription:=0D=0Ahttp://www=2Epostgr=
esql=2Eorg/mailpref/pgsql-novice=0D=0A=0D=0A=0D=0A=0D=0A=0D=0A-------------=
----------------------------=0D=0AThe substance of this message, including
=
any attachments, may be=0Aconfidential, legally privileged and/or exempt
fr=
om disclosure=0Apursuant to Massachusetts law=2E It is
intended=0D=0Asolely=
for the addressee=2E If you received this in error, please=0Acontact the
s=
ender and delete the material from any computer=2E=0D=0A
------_=_NextPart_001_01C8B077.32113A00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML dir=3Dltr><HEAD><TITLE>Re: [NOVICE] Disadvantages to using
"text"</TI=
TLE>=0A<META http-equiv=3DContent-Type content=3D"text/html;
charset=3Dunic=
ode">=0A<META content=3D"MSHTML 6=2E00=2E2900=2E3314"
name=3DGENERATOR></HE=
AD>=0A<BODY>=0A<DIV id=3DidOWAReplyText57489 dir=3Dltr>=0A<DIV
dir=3Dltr><F=
ONT face=3DArial color=3D#000000 size=3D2>The other disadvantage I have
not=
iced is that you can't override operator behavior of text but you
can =
for varchar=2E</FONT></DIV>=0A<DIV dir=3Dltr><FONT face=3DArial
size=3D2></=
FONT> </DIV>=0A<DIV dir=3Dltr><FONT face=3DArial size=3D2>So I have
be=
en able to override the case sensitivity of varchar fields (which is
annoyi=
ng when working with MS Access etc) simply by changing the way
L=
IKE, =3D > etc=2E are handled for varchar=2E Since text is
d=
efined in pg_catalog, it doesn't seem possible to override it or at least
h=
aven't had any success with that=2E Maybe I am missing
something=2E</=
FONT></DIV>=0A<DIV dir=3Dltr><FONT face=3DArial
size=3D2></FONT> </DIV=
>=0A<DIV dir=3Dltr><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>=0A<DIV
=
dir=3Dltr><FONT face=3DArial size=3D2>Regina</FONT></DIV>=0A<DIV
dir=3Dltr>=
<FONT face=3DArial size=3D2></FONT> </DIV></DIV>=0A<DIV
dir=3Dltr><BR>=
=0A<HR tabIndex=3D-1>=0A<FONT face=3DTahoma size=3D2><B>From:</B>
pgsql-nov=
ice-owner@[EMAIL PROTECTED]
on behalf of Greg Cocks<BR><B>Sent:</B> Wed
5/7/=
2008 1:48 PM<BR><B>To:</B> PostgreSQL List - Novice<BR><B>Subject:</B> Re:
=
[NOVICE] Disadvantages to using
"text"<BR></FONT><BR></DIV>=0A<DIV>=0A<P><F=
ONT size=3D2>One disadvantage is that if you are using MS Access as a
front=
-end via<BR>ODBC / linked tables, you can not do joins on fields set as
tex=
t (in<BR>queries, etc)<BR><BR><BR>-----Original Message-----<BR>From:
Frank=
Bax [<A
href=3D"mailto:fbax@[EMAIL PROTECTED]
">mailto:fbax@[EMAIL PROTECTED]
>=
]<BR>Sent: Wednesday, May 07, 2008 10:55 AM<BR>To: PostgreSQL List -
Novice=
<BR>Subject: Re: [NOVICE] Disadvantages to using "text"<BR><BR>Aurynn Shaw
=
wrote:<BR>> Internally, Postgres treats a VARCHAR(n) as a TEXT with a
CH=
ECK<BR>> constraint applied to it, so VARCHAR is going to be slightly
sl=
ower to<BR>use=2E<BR><BR><BR>Don't you mean VARCHAR(n) will be slightly
slo=
wer on UPDATES=2E<BR><BR>--<BR>Sent via pgsql-novice mailing list
(pgsql-no=
vice@[EMAIL PROTECTED]
)<BR>To make changes to your subscription:<BR><A
href=
=3D"http://www=2Epostgresql=2Eorg/mailpref/pgsql-novice">http://www=2Epostg=
resql=2Eorg/mailpref/pgsql-novice</A><BR><BR>--<BR>Sent via pgsql-novice
ma=
iling list (pgsql-novice@[EMAIL PROTECTED]
)<BR>To make changes to your
subsc=
ription:<BR><A
href=3D"http://www=2Epostgresql=2Eorg/mailpref/pgsql-novice"=
>http://www=2Epostgresql=2Eorg/mailpref/pgsql-novice</A><BR></FONT></P></DI=
V></BODY></HTML>=0D=0A<HTML><BODY><P><hr
size=3D1></P>=0D=0A<P><STRONG>=0D=
=0AThe substance of this message, including any attachments, may be
confide=
ntial, legally privileged and/or exempt from disclosure pursuant to
Massach=
usetts law=2E It is intended solely for the addressee=2E If you received
th=
is in error, please contact the sender and delete the material from any
com=
puter=2E=0D=0A</STRONG></P></BODY></HTML>=0D=0A=0D=0A<P><hr size=3D1></P>=
=0D=0A<P><STRONG><font size=3D"2" color=3D"339900"> Help make the earth a
g=
reener place=2E If at all possible resist printing this email and join us
i=
n saving paper=2E </p> <p>
</font></STRONG></P>=0D=0A=0D=0A=0D=0A=0D=0A=0D=
=0A=0D=0A
------_=_NextPart_001_01C8B077.32113A00--
|
