Re: [GENERAL] 'a' == 'a '
- From: "Dann Corbit" <DCorbit(at)connx(dot)com>
- To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: <Richard_D_Levine(at)raytheon(dot)com>, <general(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: [GENERAL] 'a' == 'a '
- Date: Mon, 24 Oct 2005 11:54:48 -0700
- Message-id: <D425483C2C5C9F49B5B7A41F8944154757D22B(at)postal(dot)corporate(dot)connx(dot)com>
Document the collating sequences used for the character types.
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> Sent: Monday, October 24, 2005 11:01 AM
> To: Tom Lane
> Cc: Dann Corbit; Richard_D_Levine(at)raytheon(dot)com;
general(at)postgresql(dot)org;
> pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [GENERAL] [HACKERS] 'a' == 'a '
>
>
> Is there any TODO here?
>
>
------------------------------------------------------------------------
--
> -
>
> Tom Lane wrote:
> > "Dann Corbit" <DCorbit(at)connx(dot)com> writes:
> > > I guess that additional ambiguity arises if you add additional
spaces
> to
> > > the end. Many database systems solve this by trimming the
characters
> > > from the end of the string upon storage and the returned string
will
> not
> > > have any trailing blanks.
> >
> > Can you document that? ISTM that that would effectively make
char(n)
> > and varchar(n) exactly equivalent, which is ... um ... a bit stupid.
> >
> > regards, tom lane
> >
> > ---------------------------(end of
broadcast)---------------------------
> > TIP 9: In versions below 8.0, the planner will ignore your desire to
> > choose an index scan if your joining column's datatypes do
not
> > match
> >
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania
> 19073
Home |
Main Index |
Thread Index