From: | Michael Wood <esiotrot(at)gmail(dot)com> |
---|---|
To: | ta(at)lavabit(dot)com |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: RESOLVED: varchar comparison and trim() |
Date: | 2012-12-21 11:04:20 |
Message-ID: | CAP6d-HUucCsqTsqs+ymWK9nDoojfDXf-YXOYeO-kM9dFTP9bwg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi
On 21 December 2012 11:54, <ta(at)lavabit(dot)com> wrote:
>
> Considering Kevin’s answer I have chosen to stick with “the Postgres way”
> of resolving this, but here are some of my other rumblings that someone
> might find useful:
>
> This all is about converting part of (and interoperate with PG/database) a
> legacy app that uses ISAM-like fixed length data.
> So, data and queries come in containing a lot of trailing spaces.
>
> Possible solutions for this “trailing space” problem that I’ve come to:
I just skimmed your post, but how about this for another solution:
Create insert and update triggers to trim the data as it arrives in
the database? Will that do what you want?
--
Michael Wood <esiotrot(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | ta | 2012-12-21 18:51:44 | Re: RESOLVED: varchar comparison and trim() |
Previous Message | ta | 2012-12-21 09:54:16 | RESOLVED: varchar comparison and trim() |