..and be careful that it isn't in here:

select '    ' + blah from table

Larry


On 11/4/05, Nathan Maves <[EMAIL PROTECTED]> wrote:
> I think that this would be a nice to have.  You would have to do a
> regular exp match to substitute one space for two or more spaces.
>
> Nathan
>
>
> On Nov 4, 2005, at 4:12 AM, Steffen Legler (JIRA) wrote:
>
> >     [ http://issues.apache.org/jira/browse/IBATIS-143?
> > page=comments#action_12356767 ]
> >
> > Steffen Legler commented on IBATIS-143:
> > ---------------------------------------
> >
> > I think, you don't understand the issue. Dynamic built SQL has
> > nothing to do with deployment. The SQL-statements are built during
> > runtime and will be shown without any removals of blanks in the
> > log4j-logger. For debugging possible errors or for presenting the
> > logger-messages it is more comfortable to have a sql-statements
> > with only one blank and not 2 or more blanks between two words.
> >
> > Greetings from Hannover,
> >
> > Steffen
> >
> >> Remove blanks in SQL
> >> --------------------
> >>
> >>          Key: IBATIS-143
> >>          URL: http://issues.apache.org/jira/browse/IBATIS-143
> >>      Project: iBatis for Java
> >>         Type: Improvement
> >>   Components: SQL Maps
> >>  Environment: all
> >>     Reporter: Steffen Legler
> >>     Priority: Minor
> >
> >>
> >> Dynamically built SQL-Statements include a lot of blanks when
> >> using conditional
> >> elements like <isEqual>. The database doesn't care, but for
> >> logging it would be
> >> nice to have a well written sql-statement, e.g. :
> >> <update id="update" parameterClass="paramClass">
> >>      update schema.table1 set
> >>                      <isEqual property="listId" compareValue="1">
> >>                      column1 = #value#
> >>                      </isEqual>
> >>                      <isEqual property="listId" compareValue="2">
> >>                      column2 = #value#
> >>                      </isEqual>
> >>              where id=#instanceId#
> >> </update>
> >>
> >> The result of a statement looks like this;
> >>      update schema.table1 set          column1 =
> >> '123'                             where id = 1000
> >>
> >> For readability it would be nice to have something like this:
> >> update schema.table1 set column1 = '123' where id = 1000
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the
> > administrators:
> >    http://issues.apache.org/jira/secure/Administrators.jspa
> > -
> > For more information on JIRA, see:
> >    http://www.atlassian.com/software/jira
> >
>
>

Reply via email to