Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (herse.apache.org: 32.97.110.149 is neither permitted
 nor denied by domain of Stan.Bradbury@gmail.com)
Message-ID: <4672D990.5080906@gmail.com>
Date: Fri, 15 Jun 2007 11:25:20 -0700
From: Stanley Bradbury <Stan.Bradbury@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: Excess white space on SELECT
References: <1181834036.25510.5.camel@B-0459>
In-Reply-To: <1181834036.25510.5.camel@B-0459>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Sebastian Niezgoda wrote:
> Hello,
>
> I noticed that Derby does not trim any excess space on SELECT 
> statements.  I'm using iBatis to map sql to Java objects thus I am 
> forced to change my queries to trim.  Is there an easier way to do 
> this?  Is there a global setting I can use when creating/connecting to 
> Derby or something along those lines?
>
> Thanks,
>
> Sebastian 
Hi -
I'm guessing you mean 'does not trim trailing space from the data values 
returned'.  Derby should do this for VARCHAR fields but doesn't for 
fixed length datatypes.  What datatypes are you retrieving and are you 
performing conversions or concatenations in your select statements?