Michael, it's sure is a standard, and though the reason I keep claiming that the behavior is correct:-)
Now of course Oracle and some other vendors I don't care to mention love straying from the path and taking their own approach, but then call themselves SQL ## compliant. Oracle has a major trailing space problem that was discussed up and down this list many times. Peter, just look at the archives. But I think following the standard is the way to go. Ilya -----Original Message----- From: Michael Peppler To: Jeff Hunter Cc: Peter J. Holzer; '[EMAIL PROTECTED] ' Sent: 2/28/02 2:38 PM Subject: Re: Whitespace being truncated with Oracle Jeff Hunter writes: > I agree, it should be fixed. > > Peter J. Holzer wrote: > > >I don't think the current behaviour[1] is correct. In perl, strings can > >have trailing spaces: "test" and "test " compare as not equal. > >In Oracle varchar2 can store strailing spaces: If I store 'test ' in a > >varchar2 column, I get back 'test ' and not 'test' or 'test '. Are you *sure* that you get 'test ' back??? I'm not be an Oracle specialist, but I know that trailing spaces in varchar() columns are normally removed on insert. This is definitely the case for Sybase - irrespective of the client that is used to access the data. I also seem to recall that this behaviour is a SQL standard. Michael -- Michael Peppler Data Migrations, Inc. [EMAIL PROTECTED] *or* [EMAIL PROTECTED] http://www.mbay.net/~mpeppler International Sybase User Group: http://www.isug.com
