From: Charles O'Farrell <charleso@gmail.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Subject: Re: Substring auto trim
Date: Thu, 14 Jan 2010 08:20:16 +1000
Message-ID: <65d71e1c1001131420l532f18e5o82521b2b888c7d9d@mail.gmail.com> (raw)
In-Reply-To: <4B4DAC9C020000250002E445@gw.wicourts.gov>
References: <65d71e1c1001130102j5f46299cm87477efcfd0c5a51@mail.gmail.com>
<10878.1263396935@sss.pgh.pa.us>
<4B4D9A0F020000250002E432@gw.wicourts.gov>
<14774.1263402847@sss.pgh.pa.us>
<4B4DAC9C020000250002E445@gw.wicourts.gov>
On Thu, Jan 14, 2010 at 3:21 AM, Kevin Grittner <Kevin.Grittner@wicourts.gov
> wrote:
>
> I'm inclined to agree with you, but it does present a barrier to
> those migrating. Are there any "migration considerations" documents
> where we should mention this? Standards compliance notes in the
> docs? Some form of this question seems to be asked frequently....
>
>
Many thanks for the quick and detailed responses. Looks like we'll have to
stick with that work around for now.
Part of the problem for us re: varchars is that we are using Cobol where
trailing spaces are significant and litter all our data and queries.
Thanks again.
Charles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: charleso@gmail.com, Kevin.Grittner@wicourts.gov, tgl@sss.pgh.pa.us
Subject: Re: Substring auto trim
In-Reply-To: <65d71e1c1001131420l532f18e5o82521b2b888c7d9d@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox